Releases: cloudposse/github-action-atmos-terraform-apply
Releases · cloudposse/github-action-atmos-terraform-apply
v1.5.0
Update infracost/actions action to v3 @renovate (#41)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
infracost/actions | action | major | v2 -> v3 |
Release Notes
v1.4.0
v1.3.0
v1.2.0
v1.1.0
v1.0.1
Added terraform output to summary @goruha (#34)
what
- Add the ability to display terraform outputs after
apply
chore: updated readme @milldr (#32)
what
- updated readme
why
- corrected job name (apply)
- added reference for docs
- pulled in content from atmos docs
make readme
references
- cloudposse/atmos#500
- closes #31
v1.0.0
Move to GitOps Config File @goruha (#29)
What
- Use configuration file
Why
- Make DRY workflows
Migrating from v1
to v2
v2
drop component-path
variable. Now it fetches from atmos.yaml
file automatically.
v2
moved variables from inputs
to atmos gitops config path ./.github/config/atmos-gitops.yaml
name |
---|
atmos-version |
atmos-config-path |
terraform-state-bucket |
terraform-state-table |
terraform-state-role |
terraform-plan-role |
terraform-apply-role |
terraform-version |
aws-region |
enable-infracost |
If you want the same behavior in v2
as inv1
you should create config ./.github/config/atmos-gitops.yaml
with the same variables as in v1
inputs.
- name: Terraform apply
uses: cloudposse/github-action-atmos-terraform-apply@v2
with:
atmos-gitops-config-path: ./.github/config/atmos-gitops.yaml
component: "foobar"
stack: "plat-ue2-sandbox"
same behaviour as
- name: Terraform apply
uses: cloudposse/github-action-atmos-terraform-apply@v1
with:
component: "foobar"
stack: "plat-ue2-sandbox"
component-path: "components/terraform/s3-bucket"
terraform-apply-role: "arn:aws:iam::111111111111:role/acme-core-gbl-identity-gitops"
terraform-state-bucket: "acme-core-ue2-auto-gitops"
terraform-state-role: "arn:aws:iam::999999999999:role/acme-core-ue2-auto-gitops-gha"
terraform-state-table: "acme-core-ue2-auto-gitops"
aws-region: "us-east-2"