v6.0.0

Skip checkout @goruha (#59)

## what * Add skip checkout input

why

• To be consistent with the Plan and apply actions that now allow to skip checkout

references

• cloudposse/github-action-atmos-terraform-plan#92
• cloudposse/github-action-atmos-terraform-apply#62
• cloudposse/github-action-atmos-terraform-drift-remediation#21

v5.5.0

Cut new release @goruha (#58)

## what * Cut new release

why

• After rollback new release failed due to no-changes test that fail

Revert "Add skip checkout input" @goruha (#57)

## What * Reverts #56

Why

• The #56 should have been released as a major version, but was released as minor.

v5.4.0

Add skip checkout input @goruha (#56)

## what * Add skip checkout input

why

• To be consistent with the Plan and apply actions that now allow to skip checkout

references

• cloudposse/github-action-atmos-terraform-plan#92
• cloudposse/github-action-atmos-terraform-apply#62
• cloudposse/github-action-atmos-terraform-drift-remediation#21

v5.3.0

Adding new --stack parameter @jamengual (#54)

## what * Upgrade default version to 1.96.0 * Add new --stack option supported on >1.90.0

why

• To allow filter changes bystacks

references

• cloudposse/atmos#714

v5.2.0

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

## 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

• #52
• There are more reported issues showing this problem in various scenarios, for instance this one

v5.1.0

Skip AWS auth if Gitops aws configuration empty in atmos settings @goruha (#51)

## what * Skip AWS auth if Gitops aws configuration empty in atmos settings

Why

• Allow to skip AWS auth and use an external one
• Make the action cloud agnostic

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
        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("-")

v5.0.0

Added atmos-include-settings input @goruha (#50)

## what * Added atmos-include-settings input

why

• Allow group jobs by settings for matrixes

Breaking changes

• The action will work only with atmos >= 1.80.0

🤖 Automatic Updates

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

## 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

v4.0.0

feat: add IAM auth support (required for stack config templating as of atmos 1.86.2) @goruha (#48)

## what * Duplicate https://github.com//pull/46

why

*Release the feature as major release

v3.5.0

Remove aws dependency @goruha (#47)

## what * Remove `aws-actions/configure-aws-credentials`

why

• Rollback behavior [3.3.0](https://github.com/cloudposse/github-action-atmos-affected-stacks/releases/tag/v3.3.0)
• Do not lock to AWS cloud platform

v3.4.0

feat: add IAM auth support (required for stack config templating as of atmos `1.86.2`) @korenyoni (#46)

## what

• Add IAM auth support

why

• IAM auth is required for stack config templating as of atmos 1.86.2

references

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

Notes

I am not quite sure if Configure Plan AWS Credentials should be controlled by a condition. In cloudposse/github-action-atmos-terraform-plan, it is controlled by the outputs of cloudposse/github-action-atmos-get-setting. But we cannot use that action within this composite action, as the former is specific to one stack/component, whereas the latter (this repo) is not. (EDIT: it's definitely a requirement to put that step behind a condition — https://github.com/cloudposse/github-action-atmos-affected-stacks/actions/runs/10458450730)

I've added additional outputs to config, most of which are not referenced at all. However I did this in order to be consistent with cloudposse/github-action-atmos-terraform-plan.