Atmos Infrastructure Runtime

The refactoring of the scaffold command is partially implemented.

Currently, only the UI dependency has been decoupled using an interface-driven approach. Specifically, a ScaffoldUI interface has been extracted in cmd/scaffold/interfaces.go to cover the 7 *generatorUI.InitUI methods used by the command. This implementation includes a generated mock (cmd/scaffold/mock_interfaces.go) and unit tests (cmd/scaffold/scaffold_mock_test.go) for the confirm-then-retry-as-update flow.

Note: The broader architectural changes proposed in the full plan—such as the TemplateLoader/TemplateExecutor split, the standalone ScaffoldGenerator type, and the DryRunFile rendering interface—have not yet been implemented. Template-loading dependencies like templates.GetAvailableConfigurations, source.Hydrate, and setup.NewGeneratorContext still involve direct calls in cmd/scaffold/scaffold.go.

Atmos provides several capabilities that are not available in Terragrunt:

• Native Authentication: Built-in multi-cloud auth (SAML, SSO, OIDC, GitHub Actions) via atmos auth login.
• Vendoring: Pull and version external modules locally with atmos vendor pull.
• Custom Commands: Define team-specific workflows directly in YAML.
• Workflows: Orchestrate multi-step operations (chaining, conditions, parallel execution).
• Terraform Shell: Drop into a pre-configured shell for debugging with atmos terraform shell <component> -s <stack>.
• Affected Detection: Analyze Git changes to find impacted components via atmos describe affected.
• Component Validation: Validate stack configurations using JSON Schema and OPA policies.
• Stack Describe: View fully-resolved configurations with atmos describe component.
• Configuration Provenance: Trace the origin of values across the import hierarchy with atmos describe component --provenance.

Atmos provides 25 official marketplace skills that cover a wide range of infrastructure orchestration tasks. These skills are loaded automatically and can be used to augment AI capabilities within the Atmos ecosystem. Key areas covered include:

• Infrastructure & Orchestration: atmos-terraform, atmos-stacks, atmos-components, atmos-ansible, atmos-helmfile, atmos-packer.
• Security & Compliance: atmos-aws-security, atmos-validation, atmos-auth.
• Automation & Workflows: atmos-workflows, atmos-steps, atmos-hooks, atmos-gitops, atmos-custom-commands.
• Configuration & Data: atmos-config, atmos-schemas, atmos-yaml-functions, atmos-templates, atmos-stores, atmos-introspection.
• Tooling & Environment: atmos-toolchain, atmos-devcontainer, atmos-vendoring, atmos-asciicast.
• Patterns & Design: atmos-design-patterns.

Before creating custom skills, check the official catalog to see if your use case is already covered.

The aqua package provides an implementation of the ToolRegistry interface that integrates Atmos with the Aqua project's tool registry. It fetches tool metadata (asset URLs, version constraints, and platform-specific overrides) from the aqua-registry GitHub repository.

Key capabilities include:

• Metadata Fetching: Supports both packages (Aqua format) and tools (legacy format) YAML structures.
• Local Overrides: Use a tools.yaml file to define local tool versions or create aliases (e.g., tf → hashicorp/terraform).
• Version Resolution: Fetches latest versions from GitHub releases and performs semver matching.
• Asset URL Construction: Uses Go templates to dynamically build download URLs using functions like trimV, OS, Arch, and Version.

// Create registry client
registry := aqua.NewAquaRegistry()

// Load local overrides
if err := registry.LoadLocalConfig("tools.yaml"); err != nil {
    log.Fatal(err)
}

// Get tool metadata
tool, err := registry.GetTool("hashicorp", "terraform")
if err != nil {
    log.Fatal(err)
}

// Get latest version
version, err := registry.GetLatestVersion("hashicorp", "terraform")
if err != nil {
    log.Fatal(err)
}

// Build download URL
url, err := registry.BuildAssetURL(tool, version)
if err != nil {
    log.Fatal(err)
}