cloudposse/atmos v1.169.0

on GitHub

what

• Update !include YAML function
• Update Atmos JSONSchema for stack manifests validation (to take into account the !include functions)
• Add unit tests
• Update docs
  • https://atmos.tools/core-concepts/stacks/yaml-functions/include

why

Make Atmos to resolve the !include functions during the initial phase of YAML stack manifest processing (in contrast to the other YAML functions, which are processed during the very last stage of stack processing).

At this initial stage, the !include functions evaluate and substitute the contents of included files, converting them into the appropriate data types (e.g., string, boolean, map, or list) before assigning them to the corresponding sections or attributes in the Atmos stack configurations.

Key implications of this behavior:

• The !include functions facilitate stack configuration reuse by enabling modularization of common configurations.
  These configurations can reside in separate local or remote files and be referenced in multiple stack definitions,
  promoting a DRY approach.

• The functions preprocess YAML files before Atmos resolves stacks and components.
  This enables configuration Inheritance and deep-merging of stack parameters after the !include directives are expanded.

• When transitioning from plain Terraform/OpenTofu to Atmos, !include allows seamless reuse of existing variable
  files (varfiles) by referencing them in the vars sections of Atmos components:

    my-component:
      vars: !include my-component.tfvars

what

• Support the --config flag as an array of strings for atmos validate editorconfig

why

• Be consistent with our config flag. With pr #1091 config would be an array of string at the root. And this should be reflected in validate editorconfig

what

• We are restricting the usage of os.Getenv
• We are also depricating usage/enhancing function processArgsAndFlags

why

• we should start using viper.BindEnv for new env variables

what

• Fixed an issue where multiple configuration files were not loading correctly.

why

• Previously, when loading files from multiple paths, only the first file found was loaded, ignoring the rest. This update ensures all configurations are properly merged
• Now, all configuration files from each specified path are loaded and merged into the Atmos config