v3.2.0

fix: filter out 'Switched to workspace' message in terraform output @Benbentwo (#68)

## what - `atmos terraform output ... -skip-init` runs `terraform workspace` && `terraform output` - When running and outputting to a file this leads to a json file similar to the following: ``` �[0m�[32mSwitched to workspace "foo-bar".�[0m { "bucket_arn": { ... } } ``` - This PR adds a simple grep line to ensure that switch is removed from the json file.

why

• Bugfix issue with Error: invalid character '\x1b' looking for beginning of value

v3.1.0

🐛 Bug Fixes

Bugfix: Process Templates false for get-settings @Benbentwo (#66)

## what

Do not process templates when fetching settings of a component

why

Causes an issue where terraform is expected before it is installed which can fail or cause conflicting version issues.

v3.0.0

Replace describe-config for atmos-get-setting, add optional cache and azure storage options @goruha (#62)

## what * Skip AWS auth if Gitops aws configuration empty in atmos settings * Updated docs and Tests. * Fix: clean environment file from .terraform cache to avoid workspace select errors * Replace the describe config for cloudposse/github-action-atmos-get-setting * Replace If statements to check for azure repository type * Add azure blob storage and cosmos * Allow to skip checkout

Why

• Allow to skip AWS auth and use an external one
• Make the action cloud agnostic
• To support azure and better config settings
• Support stack level integration configs

Example

If atmos.yaml contains

integrations:
  github:
    gitops:
      opentofu-version: 1.7.3    
      terraform-version: 1.5.7
      infracost-enabled: false
      artifact-storage:
        region: us-east-2
        bucket: cptest-core-ue2-auto-gitops
        table: cptest-core-ue2-auto-gitops-plan-storage
# here used to be
#      role: arn:aws:iam::461333128641:role/cptest-core-ue2-auto-gha-iam-gitops-gha
# here used to be
#      role:
#        plan: arn:aws:iam::582055374050:role/cptest-core-gbl-identity-planners
#        apply: arn:aws:iam::582055374050:role/cptest-core-gbl-identity-gitops
      matrix:
        sort-by: .stack_slug
        group-by: .stack_slug | split("-") | [.[0], .[2]] | join("-")

Reference

• feature/dev-2523-make-aws-role-assumption-optional-in-github-actions

v2.5.1

fix: replace context with default var @goruha (#63)

## what - Replace context with default variable

why

• When using container within GitHub Actions, context value is incorrect. Default variable value remains correct.
• As github.action_path is used during step execution (within runner), it can be replaced by default variable.

references

• cloudposse/github-action-atmos-affected-stacks#52
• There are more reported issues showing this problem in various scenarios, for instance this one

🤖 Automatic Updates

Update .github/settings.yml @osterman (#61)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

v2.5.0

fix: assume IAM role before running `cloudposse/github-action-atmos-get-setting` @goruha (#58)

what

• assume IAM role before running cloudposse/github-action-atmos-get-setting

why

As of atmos 1.86.2, when atmos.Component began actually retrieving the TF state, it broke cloudposse/github-action-atmos-affected-stacks which we resolved as part of this release of the aforementioned action. We just had the action assume the IAM role, and that was it. However in cases where this function is used, appropriate IAM credentials to also be a requirement for cloudposse/github-action-atmos-get-setting:

> Run cloudposse/github-action-atmos-get-setting@v1
template: all-atmos-sections:163:26: executing "all-atmos-sections" at <atmos.Component>: error calling Component: exit status 1

Error: error configuring S3 Backend: IAM Role (arn:aws:iam::xxxxxxxxxxxx:role/xxxx-core-gbl-root-tfstate) cannot be assumed.

There are a number of possible causes of this - the most common are:
  * The credentials used in order to assume the role are invalid
  * The credentials do not have appropriate permission to assume the role
  * The role ARN is not valid

Error: NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors

references

https://github.com/cloudposse/atmos/releases/tag/v1.86.2

v2.4.0

Caching .terraform @goruha (#56)

## what * Cache .terraform * Consolidate atmos get settings into one action run * Made action self-contained

why

• Improve performance
• Improve performance

references

v2.3.0

Fix opentofu init on apply @goruha (#54)

## what * Move logs cat exactly after the terraform call * Use atmos to get output values JSON

why

• Improve logging info
• Inherit all terraform / tofu context from atmos

references

• DEV-2269 Update infra-live and infra-test to use opentofu

v2.2.0

Support OpenTofu @goruha (#53)

## what * Install opentofu

why

• Gitops support OpenTofu

references

• DEV-2269 Update infra-live and infra-test to use opentofu

v2.1.0

Fix terraform docs config path @goruha (#52)

## what * Fix terraform docs config path

why

• Apply failed because can not find the config

v2.0.1

Remove comments @goruha (#51)

## what * Remove commented code

why

• This is merge artifact

Fix workflows @goruha (#50)

## what * Fix workflows

why

• By mistake workflows used to be from terraform modules

Apply Summary Should Display Non-sensitive Terraform Outputs @goruha (#49)

## what * Use terraform docs to display outputs

why

• Add ability to display terraform outputs after apply.

references

• DEV-53: Apply Summary Should Display Non-sensitive Terraform Outputs
• https://github.com/cloudposse/github-action-atmos-terraform-apply/actions/runs/9875304487

🤖 Automatic Updates

Update release workflow to allow pull-requests: write @osterman (#48)

## what - Update workflow (`.github/workflows/release.yaml`) to have permission to comment on PR

why

• Add comment to PR when it is released

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#46)

## what - Update workflows (`.github/workflows/settings.yaml`) to use shared workflows from `.github` repo

why

• Reduce nested levels of reusable workflows

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#45)

## what - Update workflows (`.github/workflows/settings.yaml`)

why

• Support new readme generation workflow.
• Generate banners