cloudposse/atmos v1.178.0 on GitHub

Update `atmos terraform version` and `atmos helmfile version` commands @aknysh (#1274)

what

Update atmos terraform version and atmos helmfile version commands
Add tests
Update docs
- https://atmos.tools/cli/configuration/components/#terraform-component-behavior
- https://atmos.tools/cli/configuration/components/#helmfile-component-behavior

why

When executing atmos terraform version and atmos helmfile version commands, take into account the command setting in atmos.yaml. The command setting specifies the executable, which can be terraform, tofu, helmfile, or a path to an executable.

components:
  terraform:
    # Optional `command` specifies the executable to be called by Atmos when running Terraform commands
    # If not defined, `terraform` is used
    # Examples:
    # command: terraform
    # command: /usr/local/bin/terraform
    # command: /usr/local/bin/terraform-1.8
    # command: tofu
    # command: /usr/local/bin/tofu-1.7.1
    # Can also be set using 'ATMOS_COMPONENTS_TERRAFORM_COMMAND' ENV var, or '--terraform-command' command-line argument
    command: terraform

components:
  helmfile:
    # Optional `command` specifies the executable to be called by Atmos when running Helmfile commands
    # If not defined, `helmfile` is used
    # Examples:
    # command: helmfile
    # command: /usr/local/bin/helmfile
    # Can also be set using 'ATMOS_COMPONENTS_HELMFILE_COMMAND' ENV var, or '--helmfile-command' command-line argument
    command: helmfile

atmos terraform version

  Terraform v1.7.3
  on darwin_arm64

atmos terraform version

  OpenTofu v1.7.1
  on darwin_arm64

atmos helmfile version

  Version            v1.1.0
  Git Commit         "brew"
  Build Date         19 May 25 18:20 EDT (1 week ago)
  Commit Date        19 May 25 18:20 EDT (1 week ago)
  Dirty Build        no
  Go version         1.24.3
  Compiler           gc
  Platform           darwin/arm64

Don't use terraform workspace in `!terraform.output` when backend is `http` @astephanh (#1268)

what

Don't use terraform workspace in !terraform.output YAML function when backend is http

why

Using http backend for remote state ended in an error

Fix: Bad characters when using the `!include` function @Cerebrovinny (#1249)

what

Fixed issue with YAML processing where strings starting with # character were being interpreted as comments and returning null values
Added special handling for strings starting with # by setting them to use single-quoted style in YAML nodes

why

Strings starting with # were being incorrectly processed as comments in YAML, causing the !include function to return null values
This was causing unexpected behavior when users tried to include values that started with the # character
Ensure that all strings starting with # are properly preserved throughout YAML processing