Vegastack Cli
Give Claude accurate Terraform resource schemas and HCL patterns for 31 cloud providers without web search or hallucinated argument names.
Overview
vegastack-cli is a plugin marketplace for the Build phase that exposes a local Terraform docs harness for 31 providers inside Claude Code.
What is this marketplace?
- Terraform docs harness covering 31 providers including AWS, Azure, GCP, Cloudflare, Kubernetes, Helm, Vault
- Resource names, argument schemas, import syntax, deprecation flags, and HCL examples offline
- Recent-change knowledge cards, cross-provider recipes, and concept-alias resolution
- Deterministic local answers without MCPs or web search (per marketplace description)
- MIT-licensed vegastack-cli plugin v0.1.9 from VegaStack Engineering
- 1 plugin in marketplace
- 31 Terraform providers documented in harness
- Plugin version 0.1.9 MIT license
Community signal: 2 GitHub stars.
What problem does it solve?
Coding agents often guess Terraform resource shapes and miss deprecations, forcing you to verify every block in provider docs.
Who is it for?
Solo devs shipping multi-cloud Terraform who want offline-accurate provider facts in Claude Code sessions.
Skip if: Pure application developers with no IaC, or teams that standardize on Pulumi/CDK only and will not touch HCL.
What do I get? / Deliverables
After install, Claude can cite accurate provider resource metadata, examples, and recipes from the harness while you author or fix IaC.
- Enabled vegastack-cli plugin
- Structured Terraform provider knowledge in agent sessions
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Infrastructure-as-code work peaks while wiring cloud integrations during Build, before repeated Ship and Operate changes. Provider harnesses are integration surfaces—AWS, Azure, GCP, Kubernetes, Helm, Vault, and allied stacks.
How it compares
Offline Terraform knowledge harness plugin, not a deploy runner or generic Development Tools skill pack.
Common Questions / FAQ
Who is Vegastack Cli for?
Builders and agents working in Terraform/HCL who need dependable provider schemas across AWS, Azure, GCP, Kubernetes, and dozens of allied providers.
When should I use Vegastack Cli?
Use it while drafting or refactoring IaC, validating imports, or comparing cross-provider patterns before apply in CI or production.
How do I add Vegastack Cli to my agent?
Add the VegaStack Vegastack Cli Claude Code marketplace, enable the Vegastack Cli plugin, and invoke it during Terraform tasks per plugin docs on GitHub.