cloudposse/atmos v1.188.0

on GitHub

what

• Update atmos describe affected and atmos describe dependents commands
• Update docs
• Add tests

why

• atmos describe affected --include dependents should respect the flags --process-templates and --process-functions in the dependent components

  • atmos describe affected --include dependents will process templates and YAML functions in the affected components and in the dependents

  • atmos describe affected --include dependents --process-templates=false --process-functions=false will not process templates and YAML functions in the affected components and in the dependents for each affected component

• Add --exclude-locked flag to atmos describe affected

  • atmos describe affected --exclude-locked will not process the locked components (metadata.locked: true) and will not show them in the results. Refer to https://atmos.tools/core-concepts/stacks/define-components/#locking-components-with-metadatalocked for more details

• Add --process-templates and --process-functions flags to atmos describe dependents to explicitly disable templates and YAML functions processing (similar to atmos describe affected)

  • atmos describe dependents will process templates and YAML functions in all components
  • atmos describe dependents --process-templates=false --process-functions=false will not process templates and YAML functions in all components

what

• Fix workflow path for workflow error message

why

• If the workflow is in a subdirectory, we need to return the path to the workflow, starting from the workflow base dir

What

• Updates the workflow utils so that when a workflow-level stack is provided, the generated -s <stack> flag is placed before any -- argument in the command args (instead of always at the end).

The -- marker indicates the end of Atmos CLI arguments; anything after it is passed directly to the underlying tool or script. Appending -s <stack> after -- caused the stack flag to be ignored in such cases.

Why

Before

atmos workflow deploy -- foo bar
# produces args: ["deploy", "--", "foo", "bar", "-s", "my-stack"]
# "-s my-stack" is ignored since it's after `--`

After

atmos workflow deploy -- foo bar
# produces args: ["deploy", "-s", "my-stack", "--", "foo", "bar"]
# stack flag is correctly passed to Atmos