feat: Add metadata inheritance and metadata.name for workspace key prefix #1812

osterman · 2025-11-22T13:28:13Z

what

Feature Implementation:

Add metadata inheritance from base components with deep-merge semantics (enabled by default via stacks.inherit.metadata)
Add metadata.name as a stable logical component identity for workspace key prefixes
Update workspace key generation precedence: explicit backend prefix → metadata.name → component identity → component path
Expose new inherit field in atmos describe config output

Bug Fixes:

Exclude metadata.type: abstract from inheritance to prevent abstract components from becoming deployable
Apply metadata inheritance in ExecuteDescribeStacks to ensure inherited metadata fields (like terraform_workspace) are resolved when describing stacks
Handle precedence conflicts: explicit terraform_workspace takes precedence over inherited/imported patterns

Documentation:

Document metadata.name convention: first-level component folder relative to component base path
Eliminate manual workspace_key_prefix patterns across version management documentation
Update all design patterns (folder-based versioning, git flow, release tracks, strict pinning) to use catalog inheritance with metadata.name
Add PRDs for metadata inheritance and workspace key prefixes
Improve version management best practices to promote inherited metadata.name over manual settings

Tests:

Add comprehensive test coverage for metadata inheritance scenarios
Add tests for workspace key generation with metadata.name
Add regression test for metadata.type: abstract exclusion
Update snapshots for new stacks.inherit field in describe config output

why

Feature Justification:

Metadata inheritance eliminates repetition across component hierarchies by allowing base components to define shared metadata (workspace configuration, Spacelift settings, etc.)
metadata.name provides a stable, predictable workspace key that doesn't change when component paths are refactored
Default-enabled inheritance with deep-merge semantics ensures components automatically inherit metadata while allowing explicit overrides

Bug Justification:

Without excluding metadata.type: abstract, abstract base components could become deployable when inherited, breaking the abstract component pattern
ExecuteDescribeStacks was only merging YAML imports but not applying component inheritance, causing inherited metadata fields to be ignored
Pattern/template metadata from imports/inheritance could override explicit workspace values due to precedence order in BuildTerraformWorkspace

Documentation Justification:

The metadata.name feature was implemented but documentation still showed old manual workspace_key_prefix patterns, creating confusion and encouraging error-prone workarounds
Creates a clear, consistent convention: metadata.name = top-level component folder
Makes documentation DRY by showing catalog patterns that inherit the stable key

references

Implements PRD: Metadata Inheritance
Implements PRD: Workspace Key Prefixes with metadata.name
Fixes TestDescribeStacksWithFilter7 which validates inherited terraform_workspace metadata

Summary by CodeRabbit

New Features
- Metadata now inherits from base components by default with deep-merge semantics.
- Added metadata.name as a stable logical component identity for stable workspace keys.
Behavior / Bug Fixes
- Workspace key generation priority: explicit backend prefix → metadata.name → component identity/path.
- metadata.inherits and abstract-typed metadata are not inherited; component values win on conflict.
- Describe/preview flows reflect merged metadata for workspace keys.
Configuration
- stacks.inherit.metadata option to disable metadata inheritance (enabled by default).
Documentation
- New docs, migration guidance, examples, and blog posts.
Tests
- Expanded tests covering inheritance, merging, and workspace-key scenarios.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Introduces a design proposal for making metadata fields inheritable from base components, solving the versioned component state management problem. Key changes: - New `stacks.inherit.metadata` configuration option (default: true) - All metadata fields inherit except `metadata.inherits` - New `metadata.name` field for logical component identity - Updated workspace_key_prefix auto-generation to use metadata.name This enables DRY patterns for versioned components where the logical identity (for state keys) can be defined once in a base component and inherited by all derived components. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>

Introduces a design proposal for using metadata.name as the logical component identity in workspace_key_prefix auto-generation. Key points: - New metadata.name field represents logical component identity - Priority: explicit config > metadata.name > metadata.component > Atmos name - Fully backwards compatible - falls back to current behavior if not set - Solves versioned component state stability problem - Works with metadata inheritance for DRY configuration 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>

🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>

…efix This implements the metadata inheritance feature and workspace_key_prefix calculation improvements: - Add `stacks.inherit.metadata` configuration option (default: true) - Make metadata inheritable from base components (except `metadata.inherits`) - Add `metadata.name` field for logical component identity - Update workspace_key_prefix auto-generation priority: 1. Explicit backend config 2. metadata.name (new) 3. metadata.component 4. Atmos component name This enables versioned component patterns where state remains stable across version upgrades (e.g., vpc/v1 -> vpc/v2) when using metadata.name. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>

- Add metadata to list of inherited sections in inheritance docs - Document stacks.inherit.metadata configuration option - Update folder-based versioning to use metadata.name pattern - Remove incorrect settings.workspace_key_prefix examples - Add blog posts for metadata inheritance and stable workspace keys 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>

…e_key_prefix pattern - Add explicit convention that metadata.name should use top-level component folder - Document convention in blog post and version management docs - Replace manual workspace_key_prefix patterns with inherited metadata.name in: - git-flow-branches-as-channels.mdx (catalog inheritance pattern) - release-tracks-channels.mdx (both track organization approaches) - terraform-workspace.mdx (add recommended section before advanced) - version-management/index.mdx (best practices) - continuous-version-deployment.mdx (planned divergence examples) - strict-version-pinning.mdx (catalog pattern for versioned components) - folder-based-versioning.mdx (convention callout) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>

mergify · 2025-11-22T13:28:49Z

Warning

This PR exceeds the recommended limit of 1,000 lines.

Large PRs are difficult to review and may be rejected due to their size.

Please verify that this PR does not address multiple issues.
Consider refactoring it into smaller, more focused PRs to facilitate a smoother review process.

github-actions · 2025-11-22T13:29:14Z

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Files

None

coderabbitai · 2025-11-22T13:49:32Z

📝 Walkthrough

Walkthrough

Adds default-on metadata inheritance (opt-out via stacks.inherit.metadata), introduces metadata.name for stable logical component identity, deep-merges base and component metadata (component wins; excludes metadata.inherits and metadata.type: abstract), and threads merged metadata into Terraform backend defaulting to prioritize metadata.name for workspace key/prefix generation.

Changes

Cohort / File(s)	Summary
Schema & config types `pkg/schema/schema.go`	Add `StacksInherit` + `Stacks.Inherit` and `IsMetadataInheritanceEnabled()`; add `BaseComponentMetadata` to base component config.
Public JSON schema `pkg/datafetcher/schema/stacks/stack-config/1.0.json`	Add `metadata.name` property; update `custom` description to reflect inheritance when enabled.
Component/result helpers `internal/exec/stack_processor_process_stacks_helpers.go`, `internal/exec/stack_processor_process_stacks_helpers_inheritance.go`	Add `BaseComponentMetadata map[string]any` to `ComponentProcessorResult`; propagate base metadata in inheritance initialization/application.
Metadata merge & inheritance `internal/exec/stack_processor_merge.go`, `internal/exec/stack_processor_utils.go`, `internal/exec/metadata_inheritance_test.go`	Implement metadata inheritance merging (filter `metadata.inherits`, exclude `type: abstract`), deep-merge semantics, and tests covering name inheritance, abstract exclusion, non-inheritance of `inherits`, toggle, nested merges, and upgrade scenarios.
Backend processing — thread metadata `internal/exec/stack_processor_backend.go`, `internal/exec/stack_processor_backend_test.go`	Thread merged metadata via `componentMetadata` in `terraformBackendConfig`; update S3/GCS/Azure default functions to accept `metadata`; compute workspace key/prefix priority: explicit backend > `metadata.name` > `metadata.component` > Atmos component name; add tests (precedence, slash normalization).
Describe / processing path `internal/exec/describe_stacks.go`	Merge base metadata into component metadata during describe/processing when inheritance enabled; ensure explicit `terraform_workspace` overrides inherited templates/patterns.
Docs — core, CLI, patterns & blog website docs & blog (multiple `website/.../*.mdx`)	Document metadata inheritance rules and exceptions, recommend `metadata.name` for stable workspace keys, add catalog-based examples, migration guidance, and update backend/workspace docs and CLI guidance.
Design patterns / examples `website/docs/design-patterns/version-management/.mdx`, `stacks/catalog/.yaml`, updated stack examples	Introduce catalog base components and examples using inheritance-driven stable workspace keys (use `metadata.name` instead of embedding versions).
Snapshots / CLI output `tests/snapshots/TestCLICommands_atmos_describe_config.stdout.golden`	Add new `inherit` object in stacks config snapshot (schema surface).

Sequence Diagram(s)

sequenceDiagram
    autonumber
    participant SP as StackProcessor
    participant Base as BaseConfigLoader
    participant Merge as MetadataMerge
    participant Backend as BackendDefaults
    participant Out as Output/Describe

    SP->>Base: load base & component configs
    SP->>SP: check stacks.inherit.metadata (default: true)
    alt inheritance enabled
        SP->>Merge: mergeMetadata(baseMetadata, componentMetadata)
        Merge->>Merge: filter base (exclude inherits / type: abstract)
        Merge->>Merge: deep-merge, overlay component (component wins)
        Merge-->>SP: finalComponentMetadata
    else inheritance disabled
        SP-->>SP: finalComponentMetadata = componentMetadata
    end
    SP->>Out: write finalComponentMetadata into component map
    SP->>Backend: processTerraformBackend(finalComponentMetadata)
    Backend->>Backend: compute workspace key/prefix:
    Backend->>Backend: 1) explicit backend value?
    alt explicit present
        Backend-->>Out: use explicit
    else
        Backend->>Backend: 2) metadata.name?
        alt metadata.name present
            Backend-->>Out: use metadata.name (slashes -> -)
        else
            Backend->>Backend: 3) metadata.component?
            alt metadata.component present
                Backend-->>Out: use metadata.component (slashes -> -)
            else
                Backend-->>Out: use Atmos component name
            end
        end
    end

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~50 minutes

Focus review areas:
- Metadata merging logic and exclusion rules in internal/exec/stack_processor_merge.go and internal/exec/stack_processor_utils.go.
- Backend default functions and updated call sites/signatures in internal/exec/stack_processor_backend.go.
- Tests in internal/exec/* covering priority, edge cases (nil/empty metadata, slash normalization), and metadata.type/metadata.inherits behavior.
- Schema/JSON changes alignment with Go types in pkg/schema and pkg/datafetcher/schema/.../1.0.json.

Possibly related PRs

Fix component inheritance: restore default behavior for metadata.component #1614 — closely related work on metadata inheritance and backend key resolution.
Improve Atmos Auth #1602 — overlaps in backend-defaulting and threading metadata through backend logic.
Update providers and hooks sections #1188 — related propagation of base-component fields through stack processing (inheritance plumbing).

Suggested labels

major

Suggested reviewers

aknysh
kevcube
goruha

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately captures the main feature: metadata inheritance and metadata.name for workspace key prefix calculation—the core runtime changes in this PR.
Docstring Coverage	✅ Passed	Docstring coverage is 90.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch osterman/metadata-inheritance-prd

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

website/docs/design-patterns/version-management/continuous-version-deployment.mdx (1)
236-244: Please drop the old workspace_key_prefix guidance

The example still tells readers to set settings.workspace_key_prefix, which is the manual pattern this PR is retiring. To stay consistent, show the stable identity via metadata.name (or inherit from the catalog base) and remove the explicit prefix override. That keeps the doc aligned with the new metadata.name convention.
     vpc:
       metadata:
-        component: vpc-experiment  # Pin dev to experiment
-      settings:
-        workspace_key_prefix: "vpc"  # Keep stable across experiments
+        name: vpc  # Stable identity across experiments
+        component: vpc-experiment  # Pin dev to experiment

🧹 Nitpick comments (3)

pkg/schema/schema.go (1)
438-445: Stacks inheritance surface and default metadata behavior are well-shaped

The Stacks.Inherit struct plus StacksInherit.IsMetadataInheritanceEnabled() giving a default of true lines up cleanly with the docs (“enabled by default, opt-out via atmos.yaml”) and keeps the config surface explicit while preserving sane zero-values.

If you ever want extra nil-safety, you could switch the receiver to a value to allow var s *StacksInherit callers without risking a panic:
-func (s *StacksInherit) IsMetadataInheritanceEnabled() bool {
-	if s.Metadata == nil {
+func (s StacksInherit) IsMetadataInheritanceEnabled() bool {
+	if s.Metadata == nil {
 		return true
 	}
-	return *s.Metadata
+	return *s.Metadata
}
Also applies to: 447-462
docs/prd/metadata-inheritance.md (2)
26-26: Minor wording simplification.

The phrase "each component must define" is slightly redundant since ownership is implied. Consider: "each component must explicitly define its own metadata" → "metadata cannot be inherited from base components."

352-352: Add missing punctuation.

Line 352 (the Exclude metadata.inherits... bullet) is missing a period at the end of the paragraph following the code block.

Apply this minor fix:
-   - Exclude `metadata.inherits` from being inherited
+   - Exclude `metadata.inherits` from being inherited.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 77768f5 and 186d45b.

📒 Files selected for processing (20)

docs/prd/metadata-inheritance.md (1 hunks)
docs/prd/workspace-key-prefixes.md (1 hunks)
internal/exec/stack_processor_backend.go (4 hunks)
internal/exec/stack_processor_backend_test.go (2 hunks)
internal/exec/stack_processor_merge.go (3 hunks)
internal/exec/stack_processor_process_stacks_helpers.go (1 hunks)
internal/exec/stack_processor_process_stacks_helpers_inheritance.go (2 hunks)
internal/exec/stack_processor_utils.go (1 hunks)
pkg/datafetcher/schema/stacks/stack-config/1.0.json (2 hunks)
pkg/schema/schema.go (2 hunks)
website/blog/2025-11-21-metadata-inheritance.mdx (1 hunks)
website/blog/2025-11-21-metadata-name-workspace-keys.mdx (1 hunks)
website/docs/cli/commands/terraform/terraform-workspace.mdx (1 hunks)
website/docs/core-concepts/stacks/inheritance/inheritance.mdx (3 hunks)
website/docs/design-patterns/version-management/continuous-version-deployment.mdx (2 hunks)
website/docs/design-patterns/version-management/folder-based-versioning.mdx (6 hunks)
website/docs/design-patterns/version-management/git-flow-branches-as-channels.mdx (3 hunks)
website/docs/design-patterns/version-management/index.mdx (1 hunks)
website/docs/design-patterns/version-management/release-tracks-channels.mdx (2 hunks)
website/docs/design-patterns/version-management/strict-version-pinning.mdx (1 hunks)

🧰 Additional context used

🧠 Learnings (14)

📓 Common learnings

Learnt from: Listener430
Repo: cloudposse/atmos PR: 934
File: tests/fixtures/scenarios/docs-generate/README.md.gotmpl:99-118
Timestamp: 2025-01-25T03:51:57.689Z
Learning: For the cloudposse/atmos repository, changes to template contents should be handled in dedicated PRs and are typically considered out of scope for PRs focused on other objectives.

📚 Learning: 2025-09-29T02:20:11.636Z

Learnt from: aknysh
Repo: cloudposse/atmos PR: 1540
File: internal/exec/validate_component.go:117-118
Timestamp: 2025-09-29T02:20:11.636Z
Learning: The ValidateComponent function in internal/exec/validate_component.go had its componentSection parameter type refined from `any` to `map[string]any` without adding new parameters. This is a type safety improvement, not a signature change requiring call site updates.

Applied to files:

internal/exec/stack_processor_process_stacks_helpers.go
internal/exec/stack_processor_backend.go
internal/exec/stack_processor_process_stacks_helpers_inheritance.go
internal/exec/stack_processor_merge.go

📚 Learning: 2025-10-08T06:48:07.499Z

Learnt from: aknysh
Repo: cloudposse/atmos PR: 1602
File: internal/exec/stack_processor_utils.go:968-1003
Timestamp: 2025-10-08T06:48:07.499Z
Learning: The `FindComponentDependenciesLegacy` function in `internal/exec/stack_processor_utils.go` is legacy code that is not actively used and is kept only for backward compatibility purposes.

Applied to files:

internal/exec/stack_processor_process_stacks_helpers.go
internal/exec/stack_processor_backend.go
internal/exec/stack_processor_utils.go
internal/exec/stack_processor_merge.go

📚 Learning: 2024-12-08T14:26:16.972Z

Learnt from: pkbhowmick
Repo: cloudposse/atmos PR: 828
File: pkg/schema/schema.go:98-100
Timestamp: 2024-12-08T14:26:16.972Z
Learning: The `ListConfig` columns array in the `Components` struct can be empty.

Applied to files:

internal/exec/stack_processor_process_stacks_helpers.go

📚 Learning: 2024-11-02T15:35:09.958Z

Learnt from: aknysh
Repo: cloudposse/atmos PR: 759
File: internal/exec/terraform.go:366-368
Timestamp: 2024-11-02T15:35:09.958Z
Learning: In `internal/exec/terraform.go`, the workspace cleaning code under both the general execution path and within the `case "init":` block is intentionally duplicated because the code execution paths are different. The `.terraform/environment` file should be deleted before executing `terraform init` in both scenarios to ensure a clean state.

Applied to files:

website/docs/cli/commands/terraform/terraform-workspace.mdx
website/docs/design-patterns/version-management/folder-based-versioning.mdx

📚 Learning: 2024-12-03T03:49:30.395Z

Learnt from: aknysh
Repo: cloudposse/atmos PR: 810
File: website/docs/core-concepts/stacks/yaml-functions/terraform.output.mdx:104-110
Timestamp: 2024-12-03T03:49:30.395Z
Learning: In the documentation for `!terraform.output`, warnings about template variable availability are already covered in other sections, so no need to suggest adding them here.

Applied to files:

website/docs/cli/commands/terraform/terraform-workspace.mdx

📚 Learning: 2025-08-29T20:57:35.423Z

Learnt from: osterman
Repo: cloudposse/atmos PR: 1433
File: cmd/theme_list.go:33-36
Timestamp: 2025-08-29T20:57:35.423Z
Learning: In the Atmos codebase, avoid using viper.SetEnvPrefix("ATMOS") with viper.AutomaticEnv() because canonical environment variable names are not exclusive to Atmos and could cause conflicts. Instead, use selective environment variable binding through the setEnv function in pkg/config/load.go with bindEnv(v, "config.key", "ENV_VAR_NAME") for specific environment variables.

Applied to files:

website/docs/cli/commands/terraform/terraform-workspace.mdx

📚 Learning: 2024-12-01T00:33:20.298Z

Learnt from: aknysh
Repo: cloudposse/atmos PR: 810
File: examples/tests/stacks/catalog/terraform/template-functions-test2/defaults.yaml:28-32
Timestamp: 2024-12-01T00:33:20.298Z
Learning: In `examples/tests/stacks/catalog/terraform/template-functions-test2/defaults.yaml`, `!exec atmos terraform output` is used in examples to demonstrate its usage, even though `!terraform.output` is the recommended approach according to the documentation.

Applied to files:

website/docs/cli/commands/terraform/terraform-workspace.mdx
website/docs/design-patterns/version-management/release-tracks-channels.mdx

📚 Learning: 2025-10-07T00:25:16.333Z

Learnt from: osterman
Repo: cloudposse/atmos PR: 1498
File: website/src/components/Screengrabs/atmos-terraform-metadata--help.html:25-55
Timestamp: 2025-10-07T00:25:16.333Z
Learning: In Atmos CLI, subcommands inherit flags from their parent commands via Cobra's command inheritance. For example, `atmos terraform metadata --help` shows `--affected` and related flags inherited from the parent `terraform` command (defined in cmd/terraform.go), even though the metadata subcommand doesn't explicitly define these flags. This is expected Cobra behavior and auto-generated help screengrabs accurately reflect this inheritance.

Applied to files:

website/blog/2025-11-21-metadata-inheritance.mdx
docs/prd/metadata-inheritance.md
internal/exec/stack_processor_utils.go
website/docs/core-concepts/stacks/inheritance/inheritance.mdx

📚 Learning: 2025-11-10T23:23:39.771Z

Learnt from: osterman
Repo: cloudposse/atmos PR: 1686
File: toolchain/registry/aqua/aqua_test.go:417-442
Timestamp: 2025-11-10T23:23:39.771Z
Learning: In Atmos toolchain AquaRegistry, tests should not hit real GitHub. Use the options pattern via WithGitHubBaseURL to inject an httptest server URL and make GetLatestVersion/GetAvailableVersions deterministic.

Applied to files:

internal/exec/stack_processor_backend_test.go

📚 Learning: 2025-11-08T19:56:18.660Z

Learnt from: osterman
Repo: cloudposse/atmos PR: 1697
File: internal/exec/oci_utils.go:0-0
Timestamp: 2025-11-08T19:56:18.660Z
Learning: In the Atmos codebase, when a function receives an `*schema.AtmosConfiguration` parameter, it should read configuration values from `atmosConfig.Settings` fields rather than using direct `os.Getenv()` or `viper.GetString()` calls. The Atmos pattern is: viper.BindEnv in cmd/root.go binds environment variables → Viper unmarshals into atmosConfig.Settings via mapstructure → business logic reads from the Settings struct. This provides centralized config management, respects precedence, and enables testability. Example: `atmosConfig.Settings.AtmosGithubToken` instead of `os.Getenv("ATMOS_GITHUB_TOKEN")` in functions like `getGHCRAuth` in internal/exec/oci_utils.go.

Applied to files:

internal/exec/stack_processor_backend.go

📚 Learning: 2025-10-13T18:13:54.020Z

Learnt from: aknysh
Repo: cloudposse/atmos PR: 1622
File: pkg/perf/perf.go:140-184
Timestamp: 2025-10-13T18:13:54.020Z
Learning: In pkg/perf/perf.go, the `trackWithSimpleStack` function intentionally skips ownership checks at call stack depth > 1 to avoid expensive `getGoroutineID()` calls on every nested function. This is a performance optimization for the common single-goroutine execution case (most Atmos commands), accepting the rare edge case of potential metric corruption if multi-goroutine execution occurs at depth > 1. The ~19× performance improvement justifies this trade-off.

Applied to files:

internal/exec/stack_processor_utils.go

📚 Learning: 2024-11-13T21:37:07.852Z

Learnt from: Cerebrovinny
Repo: cloudposse/atmos PR: 764
File: internal/exec/describe_stacks.go:289-295
Timestamp: 2024-11-13T21:37:07.852Z
Learning: In the `internal/exec/describe_stacks.go` file of the `atmos` project written in Go, avoid extracting the stack name handling logic into a helper function within the `ExecuteDescribeStacks` method, even if the logic appears duplicated.

Applied to files:

internal/exec/stack_processor_utils.go

📚 Learning: 2024-12-07T16:16:13.038Z

Learnt from: Listener430
Repo: cloudposse/atmos PR: 825
File: internal/exec/helmfile_generate_varfile.go:28-31
Timestamp: 2024-12-07T16:16:13.038Z
Learning: In `internal/exec/helmfile_generate_varfile.go`, the `--help` command (`./atmos helmfile generate varfile --help`) works correctly without requiring stack configurations, and the only change needed was to make `ProcessCommandLineArgs` exportable by capitalizing its name.

Applied to files:

internal/exec/stack_processor_utils.go

🧬 Code graph analysis (3)

internal/exec/stack_processor_backend_test.go (1)

pkg/schema/schema.go (1)

AtmosConfiguration (53-94)

internal/exec/stack_processor_utils.go (3)

pkg/schema/schema.go (1)

Stacks (438-445)

pkg/config/const.go (1)

InheritsSectionName (102-102)

pkg/merge/merge.go (1)

Merge (389-427)

internal/exec/stack_processor_merge.go (3)

pkg/schema/schema.go (1)

Stacks (438-445)

pkg/merge/merge.go (1)

Merge (389-427)

pkg/config/const.go (1)

MetadataSectionName (75-75)

🪛 GitHub Actions: Website Preview Build

website/blog/2025-11-21-metadata-name-workspace-keys.mdx