cloudposse/atmos v1.145.0

on GitHub

what

• Added support for metadata.locked with components

• Separate atmos CLI tests into many files: tests/test_cases.yaml --> tests/test-cases/*.yaml

why

• The metadata.locked parameter prevents changes to a component while still allowing read operations. When a component is locked, operations that would modify infrastructure (like terraform apply) are blocked, while read-only operations (like terraform plan) remain available. By default, components are unlocked. Setting metadata.locked to true prevents any change operations.

# Lock a production database component to prevent accidental changes
components:
  terraform:
    rds:
      metadata:
        locked: true
      vars:
        name: production-database