v1.16.1

Issues | Pull Requests | v1.16.0...v1.16.1 | Base revision

Bug Fixes

#2471 create-scaffold-pr: install ghcp

v1.16.0

Issues | Pull Requests | v1.15.5...v1.16.0 | Base revision

Features

#2431 Follow-up PR Group Labels

This feature is disabled by default.

You can add pull request labels to group original pull requests and follow-up pull requests.

tfaction-root.yaml:

follow_up_pr_group_label:
  enabled: true # The default is false
  prefix: "tfaction:follow-up-pr-group/"

When the apply workflow fails, a pull request label is created and is added to an original pull request and new follow-up pull requests.
If the apply workflow fails again when a follow-up pull request is merged, a follow-up PR Group label of the follow-up pull request is added to a new follow-up pull request.
For instance, let's say a pull request #100 fails, and a follow-up PR #110 is created.
And a follow-up PR #110 fails, and a follow-up PR #120 is created.
In this case, a follow-up PR group label tfaction:follow-up-pr-group/100 is added to pull requests #100, #110, and #120.
These pull requests are grouped by a label tfaction:follow-up-pr-group/100.
You can search pull requests by label.

v1.15.5

Issues | Pull Requests | v1.15.4...v1.15.5 | Base revision

🐛 Bug Fixes

#2399 Fix a bug that providers_lock_opts is ignored

Others

#2399 #2401 #2402 Generate JSON Schema from code

⚠️ JSON Schema was removed from the default branch main and feature branches.
JSON Schema was added to the branch latest, pr/<pr number>, and release versions.

💡 Input Complementation by YAML Language Server

Add a code comment to tfaction-root.yaml:

# yaml-language-server: $schema=https://raw.githubusercontent.com/suzuki-shunsuke/tfaction/refs/heads/latest/schema/tfaction-root.json

If you specify a branch like latest as version, editors can't reflect the update of JSON Schema well as they cache JSON Schema.
You would need to do something like reopening the file.
So it's good to specify semver and update it periodically.

# yaml-language-server: $schema=https://raw.githubusercontent.com/suzuki-shunsuke/tfaction/refs/tags/v1.15.5/schema/tfaction-root.json

Using Renovate and our Renovate Config Preset, you can automate the update:

{
  "extends": [
    "github>suzuki-shunsuke/renovate-config:yaml-language-server#3.1.0"
  ]
}

Add a code comment to tfaction.yaml:

# yaml-language-server: $schema=https://raw.githubusercontent.com/suzuki-shunsuke/tfaction/refs/heads/latest/schema/tfaction.json

Or

# yaml-language-server: $schema=https://raw.githubusercontent.com/suzuki-shunsuke/tfaction/refs/tags/v1.15.5/schema/tfaction.json

v1.15.5-1

v1.15.5-0...v1.15.5-1 | Base revision

v1.15.5-0

v1.15.4...v1.15.5-0 | Base revision

v1.15.4

Issues | Pull Requests | v1.15.3...v1.15.4 | Base revision

#2332 Stop running google-github-actions/setup-gcloud

Warning

tfaction doesn't run google-github-actions/setup-gcloud anymore.
tfaction doesn't depend on gcloud and gsutil, so this change has no problem for tfaction.
But if you run steps depending on these tools, this change may break your workflows.
In that case, please run google-github-actions/setup-gcloud yourself.

tfaction used setup-gcloud to upload plan files to Google Cloud Storage (GCS) using gsutil.
But now tfaction uploads plan files to GitHub Artifacts instead of GCS.
So gcloud and gsutil aren't necessary anymore.

v1.15.3

Issues | Pull Requests | v1.15.2...v1.15.3 | Base revision

Fixes

#2305 Add mentions if terraform apply fails

This notifies failures of terraform apply.
If you use Slack, we recommend setting the notification.

https://github.com/settings/reminders/YOUR_ORG

You are mentioned in a comment

v1.15.2

Issues | Pull Requests | v1.15.1...v1.15.2 | Base revision

Features

#2248 Support debug mode

You can now output debug log by setting the environment variable TFACTION_DEBUG to true.

env:
  TFACTION_DEBUG: "true"

#2256 setup: Run $terraform_command providers for troubleshooting

Sometimes the output of terraform providers (or tofu providers) is useful to look into provider's version constraint.

In that case, you can now see it in the log of setup action.

e.g.

Run "$TF" providers

Providers required by configuration:
.
└── provider[registry.terraform.io/hashicorp/null] 3.2.3

v1.15.1

Issues | Pull Requests | v1.15.0...v1.15.1 | Base revision

🐛 Bug Fixes

This release fixed a bug of list-targets action.

#2243 Run terragrunt render-json on the directory where terragrunt.hcl exists
#2245 Run aqua i -l -a to create links
#2246 validate the output of terragrunt render-json
#2247 trim spaces to exclude the repository root directory

v1.15.0

Issues | Pull Requests | v1.14.0...v1.15.0 | Base revision

Features

#2196 #2203 list-targets: Enable detection of local path module updates when using Terragrunt @Taiki130

Implemented functionality to detect updates in modules referenced via Terragrunt's local path modules using terragrunt render-json command.