v1.2.2-1

v1.2.2-1...v1.2.2-1 | Base revision

Bug Fixes

#1576 #1578 test-module: Run terraform init to install providers and modules

v1.2.1

Issues | Pull Requests | v1.2.0...v1.2.1 | Base revision

Bug Fixes

#1572 apply: Fix a bug the template invalid-workflow-sha isn't found

v1.2.0

Issues | Pull Requests | v1.1.1...v1.2.0 | Base revision

Features

#1554 Support executing Terraform compatible tools such as OpenTofu and Terragrunt instead of Terraform

Caution

We don't usually use OpenTofu and Terragrunt, so we haven't done only simple verification.

https://suzuki-shunsuke.github.io/tfaction/docs/feature/use-terraform-compatible-tool/

tfaction executes Terraform commands such as terraform init, fmt, validate, plan, apply, and so on.
This release enables you to execute any tools compatible with Terraform instead of Terraform.
You can use tools such as OpenTofu and Terragrunt instead of Terraform.

How to use

You can specify a tool by the setting terraform_command in tfaction-root.yaml and tfaction.yaml.

tfaction-root.yaml

terraform_command: tofu # terragrunt
target_groups:
  - working_directory: aws/
    terraform_command: tofu # terragrunt

tfaction.yaml

terraform_command: tofu # terragrunt

Then the given command is executed instead of terraform.
For example, if terraform_command is tofu, commands such as tofu init, fmt, validate, plan, apply are executed instead of terraform.

💡 Combine OpenTofu and Terragrunt

You can also combine OpenTofu and Terragrunt.

1. Set terraform_command to terragrunt
2. Set the environment variable TERRAGRUNT_TFPATH to tofu

💡 Validate terraform_command

You can validate terraform_command in GitHub Actions Workflows.

e.g.

- uses: suzuki-shunsuke/tfaction/get-target-config@v1.2.0
  id: target-config

- run: |
    echo "::error:: terraform_command is invalid"
    exit 1
  if: |
    ! contains(fromJSON('["terraform", "terragrunt", "tofu"]'), steps.target-config.outputs.terraform_command)

v1.1.1

Issues | Pull Requests | v1.1.0...v1.1.1 | Base revision

Fixes

#1538 chore(deps): update suzuki-shunsuke/trivy-config-action action to v0.2.2

You can specify Trivy's configuration file path by the nevironment variable TRIVY_CONFIG in GitHub Actions Workflows.

env:
  TRIVY_CONFIG: ${{ github.workspace }}/trivy.yaml

v1.1.0

Issues | Pull Requests | v1.0.4...v1.1.0 | Base revision

Features

#1519 Allow conftest policy directory to be specified in global config

v1.1.0-1

v1.1.0-1...v1.1.0-1 | Base revision

Features

#1519 Allow conftest policy directory to be specified in global config

v1.0.4

Issues | Pull Requests | v1.0.3...v1.0.4 | Base revision

Bug Fixes

#1512 #1513 list-targets-with-changed-files: Fix a bug that the action list-targets-with-changed-files failed due to the error Error: "[object Object]" is not valid JSON in the apply workflow

v1.0.3

Issues | Pull Requests | v1.0.2...v1.0.3 | Base revision

Caution

This release has a critical bug. Please update to v1.0.4 or newer.
#1512

Refactoring

#1474 Format codes with prettier
#1475 Remove codes regarding the deprecated setting s3_bucket_name_plan_file
#1476 Remove codes regarding the deprecated setting gcs_bucket_name_plan_file
#1479 Refacgtor TypeScript

• Add unit tests using Jest
• Remove copy and paste and share codes properly
• Refactor TypeScript using features such as optional chaining
• Use zod

v1.0.2

Issues | Pull Requests | v1.0.1...v1.0.2 | Base revision

Bug Fixes

#1471 test: fix a bug that *.tf isn't formatted automatically by terraform fmt if the event type is pull_request_target

v1.0.1

Issues | Pull Requests | v1.0.0...v1.0.1 | Base revision

Bug Fixes

#1398 #1407 release-module: Fix a bug that tfaction can't release modules that is more than 2+ level of directories