generated from suzuki-shunsuke/tfaction-getting-started
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update suzuki-shunsuke/tfaction action to v0.7.3 (.github/workflows) #121
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update suzuki-shunsuke/tfaction action to v0.7.3 (.github/workflows) #121
renovate
wants to merge
1
commit into
main
from
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
2 times, most recently
from
October 21, 2023 06:52
fe084e9
to
f06357f
Compare
renovate
bot
changed the title
Update suzuki-shunsuke/tfaction action to v0.7.0 (.github/workflows)
Update suzuki-shunsuke/tfaction action to v0.7.2 (.github/workflows)
Oct 22, 2023
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
4 times, most recently
from
October 28, 2023 19:56
7828bdf
to
e494092
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
4 times, most recently
from
November 6, 2023 12:21
2cd0a62
to
e8a347c
Compare
renovate
bot
changed the title
Update suzuki-shunsuke/tfaction action to v0.7.2 (.github/workflows)
Update suzuki-shunsuke/tfaction action to v0.7.3 (.github/workflows)
Nov 7, 2023
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
5 times, most recently
from
November 13, 2023 18:29
788bfdd
to
a75de3e
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
7 times, most recently
from
November 18, 2023 16:56
4e3080a
to
5280fcc
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
5 times, most recently
from
November 27, 2023 22:23
5f54512
to
f228889
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
4 times, most recently
from
December 20, 2023 03:43
2d6d193
to
030fc33
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
from
December 27, 2023 15:25
030fc33
to
68f0fa1
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
3 times, most recently
from
January 11, 2024 18:43
f0ba327
to
9755611
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
2 times, most recently
from
January 22, 2024 17:04
7381b1c
to
e69b948
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
6 times, most recently
from
February 1, 2024 09:33
e0cf675
to
1594eb1
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
2 times, most recently
from
February 8, 2024 22:39
d97cf82
to
c726082
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
2 times, most recently
from
February 16, 2024 21:22
d8e0708
to
8dfa1ac
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
2 times, most recently
from
March 5, 2024 00:53
8c23b08
to
e53f025
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
3 times, most recently
from
March 14, 2024 17:05
891ac9f
to
64415c6
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
3 times, most recently
from
March 20, 2024 23:40
06bb777
to
ee23c57
Compare
renovate
bot
force-pushed
the
renovate/github/workflows-suzuki-shunsuke-tfaction-0.x
branch
from
March 22, 2024 04:56
ee23c57
to
8b320e6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.6.9
->v0.7.3
Release Notes
suzuki-shunsuke/tfaction (suzuki-shunsuke/tfaction)
v0.7.3
Compare Source
Issues | Pull Requests | suzuki-shunsuke/tfaction@v0.7.2...v0.7.3 | Base revision
Overview
Features
Support disabling to update related pull requests per pull request by pull request label
#902 #1272
https://suzuki-shunsuke.github.io/tfaction/docs/feature/auto-update-related-prs
tfaction updates related pull requests when the remote state is updated.
From this release, you can exclude specific pull requests by adding the pull request label
tfaction:disable-auto-update
.Support merging jobs for tfmigrate and terraform
#223 #1275
New actions
plan
andapply
were added.You can replace actions
terraform-plan
andtfmigrate-plan
withplan
, and can replaceterraform-apply
andtfmigrate-apply
withapply
.You can merge jobs for
tfmigrate
with jobs forterraform
.You can simplify workflows.
This pull request keeps the compatibility.
How to merge jobs
setup
jobterraform-plan
andterraform-apply
toplan
andapply
TFACTION_JOB_TYPE
terraform-plan
andterraform-apply
withplan
andapply
Please see the example too.
1. Fix outputs of
setup
jobBefore
After
4. Fix
TFACTION_JOB_TYPE
Before
After
5. Replace actions
terraform-plan
andterraform-apply
withplan
andapply
You don't need to change inputs.
Before
After
v0.7.2
Compare Source
Issues | Pull Requests | suzuki-shunsuke/tfaction@v0.7.1...v0.7.2 | Base revision
Bug Fixes
#1242 #1246 test, test-module: Fix a bug that the test succeeds even if tflint, trivy, or tfsec fails
The root cause of the bug was the bug of reviewdog.
v0.7.1
Compare Source
Issues | Pull Requests | suzuki-shunsuke/tfaction@v0.7.0...v0.7.1 | Base revision
Features
#1233 setup: Support pull_request_target
tfaction works with
pull_request_target
event.v0.7.0
Compare Source
Issues | Pull Requests | suzuki-shunsuke/tfaction@v0.6.9...v0.7.0 | Base revision
💡 This release includes significant security improvements, so we strongly recommend upgrading to v0.7.0 or later as soon as possible.
Overview
plan_workflow_name
is required intfaction-root.yaml
terraform-apply
action'sgithub_token
input, which is the GitHub Actions' token${{github.token}}
by default, requires the additional permissionactions: read
#1175 The setting
plan_workflow_name
is required intfaction-root.yaml
.e.g.
#1175
terraform-apply
action'sgithub_token
input, which is the GitHub Actions' token${{github.token}}
by default, requires the additional permissionactions: read
.How to upgrade
1.
Create a pull request to upgrade tfactionplan_workflow_name
totfaction-root.yaml
s3_bucket_name_plan_file
andgcs_bucket_name_plan_file
from tfaction-root.yaml and tfaction.yamlactions: read
toterraform-apply
action'sgithub_token
input, which is the GitHub Actions' token${{github.token}}
by defaultactions:read
to the token or Appterraform apply
: ref2.
Verify the upgrade with a working directory in the upgrade pull request3.
If CI works well, merge the pull request4.
Update all pull request branches to create plan files at GitHub Actions ArtifactsThis is an example script to update pull request branches.
If you merge a pull request without updating the pull request branch,
apply
would fail because the plan file wouldn't found at GitHub Actions Artifacts. In that case, please merge a follow up pull request, then the issue would be solved.5.
Remove unnecessary resources such as S3 or GCS buckets for plan files and permissions to access plan filesFeatures
#1175 Change the storage of plan files from S3 or GCS to GitHub Actions' Artifacts
#1174 Validate pull request workflow run's commit hash if it is same with the hash of the pull request HEAD
Change the storage of plan files from S3 or GCS to GitHub Actions' Artifacts
#1175
tfaction ever stored plan files to S3 or GCS, but tfaction v0.7.0 migrats them to GitHub Actions Artifacts.
By this change you don't have to create and manage S3 or GCS.
Furthermore, S3 or GCS had security risks that plan files could be tampered.
GitHub Actions Artifacts can be uploaded files only in the associated workflow run and can't be tampered from outside of the workflow run.
GitHub Actions Artifacts has the retention period so plan files are removed after the retension period.
The default retention period is 90 days, and we think it is enough.
Validate pull request workflow run's commit hash if it is same with the hash of the pull request HEAD
If the workflow run's commit hash is old, the workflow run would fail.
Retrying old workflow run confuses you because old workflow run's results are posted to the pull request as if the latest result.
This validation prevents old workflow run from being retried and resolves the issue.
Thank you for your support ❤️
We really appreciate your support.
We couldn't release v0.7.0 without your support.
We called for testers for this release, then many people helped us!
They conducted tests with the prerelease version. Thank you a lot!
@kyontan
@ponkio-o
@rrreeeyyy
And thank you everyone who reposted my post!
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.