cloudposse/atmos v1.50.0

on GitHub

what

• Fix processing of Spacelift stack dependencies using settings.depends_on config
• Implement double-dash -- handling for terraform and helmfile commands
• Update docs
• Update atmos terraform --help
• Update atmos helmfile --help

why

• Processing of Spacelift stack dependencies using settings.depends_on config had issues with cross-environment, cross-account dependencies

• double-dash -- can be used on the command line to signify the end of the options for Atmos and the start of the additional native arguments and flags for the terraform and helmfile commands. This allows using native terraform and helmfile arguments and flags w/o having Atmos handling it

  For example:
  - atmos terraform plan <component> -s <stack> -- -refresh=false
  - atmos terraform apply <component> -s <stack> -- -lock=false

test

export ATMOS_LOGS_LEVEL=Trace
atmos terraform plan top-level-component1 -s tenant1-ue2-dev -- -refresh=false -lock=false

Writing the variables to file:
examples/complete/components/terraform/top-level-component1/tenant1-ue2-dev-top-level-component1.terraform.tfvars.json

Executing command:
/usr/local/bin/terraform init -reconfigure

Command info:
Terraform binary: terraform
Terraform command: plan
Arguments and flags: [-refresh=false -lock=false]
Component: top-level-component1
Stack: tenant1-ue2-dev
Working dir: examples/complete/components/terraform/top-level-component1

Executing command:
/usr/local/bin/terraform workspace select tenant1-ue2-dev

Executing command:
/usr/local/bin/terraform plan -var-file tenant1-ue2-dev-top-level-component1.terraform.tfvars.json 
-out tenant1-ue2-dev-top-level-component1.planfile -refresh=false -lock=false