search

jinugasachio / terraform-workspace-type

0 stars 0 forks source link

Update dependency suzuki-shunsuke/tfcmt to v3.4.2 #92

Open renovate[bot] opened 2 years ago

renovate[bot] commented 2 years ago

This PR contains the following updates:

Package Update Change
suzuki-shunsuke/tfcmt minor v3.1.0 -> v3.4.2

Release Notes

suzuki-shunsuke/tfcmt (suzuki-shunsuke/tfcmt) ### [`v3.4.2`](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.4.2) [Compare Source](https://togithub.com/suzuki-shunsuke/tfcmt/compare/v3.4.1...v3.4.2) [Pull Requests](https://togithub.com/suzuki-shunsuke/tfcmt/pulls?q=is%3Apr+milestone%3Av3.4.2) | [Issues](https://togithub.com/suzuki-shunsuke/tfcmt/issues?q=is%3Aissue+milestone%3Av3.4.2) | https://github.com/suzuki-shunsuke/tfcmt/compare/v3.4.1...v3.4.2 #### Bug Fixes [#​451](https://togithub.com/suzuki-shunsuke/tfcmt/issues/451) Add pull request labels properly even if a pull request number isn't passed as an argument or an environment variable `tfcmt plan` gets an associated pull request from a commit hash if a pull request number isn't passed as an argument or an environment variable, and adds pull request labels according to the terraform plan result. This update has fixed a bug that a pull request label isn't added properly. If a pull request number is passed as an argument or an environment variable, this update isn't related. ### [`v3.4.1`](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.4.1) [Compare Source](https://togithub.com/suzuki-shunsuke/tfcmt/compare/v3.4.0...v3.4.1) [Pull Requests](https://togithub.com/suzuki-shunsuke/tfcmt/pulls?q=is%3Apr+milestone%3Av3.4.1) | [Issues](https://togithub.com/suzuki-shunsuke/tfcmt/issues?q=is%3Aissue+milestone%3Av3.4.1) | https://github.com/suzuki-shunsuke/tfcmt/compare/v3.4.0...v3.4.1 #### Bug Fixes [#​436](https://togithub.com/suzuki-shunsuke/tfcmt/issues/436) Fix links to GitHub Actions jobs in GitHub Enterprise #### Others [#​437](https://togithub.com/suzuki-shunsuke/tfcmt/issues/437) Update Go from v1.18.5 to v1.19.1 #### Contributors Thank you, Contributors! [@​Warashi](https://togithub.com/Warashi) [#​436](https://togithub.com/suzuki-shunsuke/tfcmt/issues/436) [@​hirosassa](https://togithub.com/hirosassa) [#​412](https://togithub.com/suzuki-shunsuke/tfcmt/issues/412) ### [`v3.4.0`](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.4.0) [Compare Source](https://togithub.com/suzuki-shunsuke/tfcmt/compare/v3.3.0...v3.4.0) [Pull Requests](https://togithub.com/suzuki-shunsuke/tfcmt/pulls?q=is%3Apr+milestone%3Av3.4.0) | [Issues](https://togithub.com/suzuki-shunsuke/tfcmt/issues?q=is%3Aissue+milestone%3Av3.4.0) | https://github.com/suzuki-shunsuke/tfcmt/compare/v3.3.0...v3.4.0 #### Features [#​387](https://togithub.com/suzuki-shunsuke/tfcmt/issues/387) [#​390](https://togithub.com/suzuki-shunsuke/tfcmt/issues/390) Create comments to pull request instead of commit GitHub no longer shows commit comments in the pull request timeline [^1]. From v3.4.0, tfcmt gets an associated pull request from commit hash and creates a comment to not commit but associated pull request. If there is no associated pull request, tfcmt sends a comment to commit. [^1]: https://github.blog/changelog/2022-08-04-commit-comments-no-longer-appear-in-the-pull-request-timeline/ ##### Example ```console $ tfcmt -v tfcmt version 3.4.0-1 (48333cac413f4500b2631eebb9703a9edc5e0a9d) $ terraform -v Terraform v1.2.6 on darwin_arm64 + provider registry.terraform.io/hashicorp/null v3.1.1 ``` ```sh export GITHUB_TOKEN=xxx export CIRCLECI=true export CIRCLE_PROJECT_USERNAME=suzuki-shunsuke export CIRCLE_PROJECT_REPONAME=test-github-action export CIRCLE_SHA1=092cda867dea7b7a229bc2dcff64aaba8fb26f8d ``` [https://github.com/suzuki-shunsuke/test-github-action/pull/104](https://togithub.com/suzuki-shunsuke/test-github-action/pull/104)/commits/092cda867dea7b7a229bc2dcff64aaba8fb26f8d ```console $ tfcmt plan -- terraform plan null_resource.foo: Refreshing state... [id=8966706083595703589] null_resource.bar: Refreshing state... [id=7780302426904623778] No changes. Your infrastructure matches the configuration. Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed. ``` 👍 tfcmt v3.4.0 creates a pull request comment. [https://github.com/suzuki-shunsuke/test-github-action/pull/104#issuecomment-1207331774](https://togithub.com/suzuki-shunsuke/test-github-action/pull/104#issuecomment-1207331774) image On the other hand, tfcmt v3.3.0 creates a commit comment. https://github.com/suzuki-shunsuke/test-github-action/commit/092cda867dea7b7a229bc2dcff64aaba8fb26f8d#commitcomment-80523712 image #### Others [#​392](https://togithub.com/suzuki-shunsuke/tfcmt/issues/392) Update Go from v1.18.4 to v1.18.5 #### Contributors Thank you, Contributors! [@​micnncim](https://togithub.com/micnncim) [#​387](https://togithub.com/suzuki-shunsuke/tfcmt/issues/387) [#​390](https://togithub.com/suzuki-shunsuke/tfcmt/issues/390) ### [`v3.3.0`](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.3.0) [Compare Source](https://togithub.com/suzuki-shunsuke/tfcmt/compare/v3.2.5...v3.3.0) [Pull Requests](https://togithub.com/suzuki-shunsuke/tfcmt/pulls?q=is%3Apr+milestone%3Av3.3.0) | [Issues](https://togithub.com/suzuki-shunsuke/tfcmt/issues?q=is%3Aissue+milestone%3Av3.3.0) | https://github.com/suzuki-shunsuke/tfcmt/compare/v3.2.5...v3.3.0 #### Features [#​376](https://togithub.com/suzuki-shunsuke/tfcmt/issues/376) Support Google Cloud Build Please set the environment variable `GOOGLE_CLOUD_BUILD`. ```sh GOOGLE_CLOUD_BUILD=true ``` And please set the following environment variables using [substitutions](https://cloud.google.com/cloud-build/docs/configuring-builds/substitute-variable-values). - `COMMIT_SHA` - `BUILD_ID` - `PROJECT_ID` - `_PR_NUMBER` - `_REGION` Please specify the repository owner and name in `tfcmt.yaml`. e.g. tfcmt.yaml ```yaml repo_owner: suzuki-shunsuke repo_name: tfcmt ``` ### [`v3.2.5`](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.2.5) [Compare Source](https://togithub.com/suzuki-shunsuke/tfcmt/compare/v3.2.4...v3.2.5) [Pull Requests](https://togithub.com/suzuki-shunsuke/tfcmt/pulls?q=is%3Apr+milestone%3Av3.2.5) | [Issues](https://togithub.com/suzuki-shunsuke/tfcmt/issues?q=is%3Aissue+milestone%3Av3.2.5) | https://github.com/suzuki-shunsuke/tfcmt/compare/v3.2.4...v3.2.5 #### Others [#​329](https://togithub.com/suzuki-shunsuke/tfcmt/issues/329) Windows Support 🎉 ### [`v3.2.4`](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.2.4) [Compare Source](https://togithub.com/suzuki-shunsuke/tfcmt/compare/v3.2.3...v3.2.4) [Pull Requests](https://togithub.com/suzuki-shunsuke/tfcmt/pulls?q=is%3Apr+milestone%3Av3.2.4) | [Issues](https://togithub.com/suzuki-shunsuke/tfcmt/issues?q=is%3Aissue+milestone%3Av3.2.4) | https://github.com/suzuki-shunsuke/tfcmt/compare/v3.2.3...v3.2.4 #### Bug Fixes [#​317](https://togithub.com/suzuki-shunsuke/tfcmt/issues/317) Set `os.Stdin` when terraform command is run This change allows you to run `terraform apply` without `-auto-approve` option. #### AS IS ```console tfcmt apply -- terraform apply -no-color null_resource.foo: Refreshing state... [id=8966706083595703589] Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create Terraform will perform the following actions: ### null_resource.bar will be created + resource "null_resource" "bar" { + id = (known after apply) } Plan: 1 to add, 0 to change, 0 to destroy. Do you want to perform these actions? Terraform will perform the actions described above. Only 'yes' will be accepted to approve. Enter a value: Error: error asking for approval: EOF ``` Do you want to perform these actions? Terraform will perform the actions described above. Only 'yes' will be accepted to approve. Enter a value: Error: error asking for approval: EOF #### TO BE ```console tfcmt apply -- terraform apply -no-color null_resource.foo: Refreshing state... [id=8966706083595703589] Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create Terraform will perform the following actions: ### null_resource.bar will be created + resource "null_resource" "bar" { + id = (known after apply) } Plan: 1 to add, 0 to change, 0 to destroy. Do you want to perform these actions? Terraform will perform the actions described above. Only 'yes' will be accepted to approve. Enter a value: yes null_resource.bar: Creating... null_resource.bar: Creation complete after 0s [id=7780302426904623778] Apply complete! Resources: 1 added, 0 changed, 0 destroyed. ``` ### [`v3.2.3`](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.2.3) [Compare Source](https://togithub.com/suzuki-shunsuke/tfcmt/compare/v3.2.2...v3.2.3) [Pull Requests](https://togithub.com/suzuki-shunsuke/tfcmt/pulls?q=is%3Apr+milestone%3Av3.2.3) | [Issues](https://togithub.com/suzuki-shunsuke/tfcmt/issues?q=is%3Aissue+milestone%3Av3.2.3) | https://github.com/suzuki-shunsuke/tfcmt/compare/v3.2.2...v3.2.3 #### Bug Fixes [#​300](https://togithub.com/suzuki-shunsuke/tfcmt/issues/300) [#​304](https://togithub.com/suzuki-shunsuke/tfcmt/issues/304) Fix the support of GitHub Enterprise. Support setting GitHub API v4 endpoint https://suzuki-shunsuke.github.io/tfcmt/github-enterprise To use tfcmt for GitHub Enterprise, please set the following fields in `tfcmt.yaml`. e.g. tfcmt.yaml ```yaml ghe_base_url: https://example.com ghe_graphql_endpoint: https://example.com/graphql ``` - https://docs.github.com/en/enterprise-server@3.5/rest/overview/resources-in-the-rest-api#current-version - https://docs.github.com/en/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint ⚠️ I ([@​suzuki-shunsuke](https://togithub.com/suzuki-shunsuke)) don't use GitHub Enterprise, so I can't confirm if it works well for GitHub Enterprise. ### [`v3.2.2`](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.2.2) [Compare Source](https://togithub.com/suzuki-shunsuke/tfcmt/compare/v3.2.1...v3.2.2) [Pull Requests](https://togithub.com/suzuki-shunsuke/tfcmt/pulls?q=is%3Apr+milestone%3Av3.2.2) | [Issues](https://togithub.com/suzuki-shunsuke/tfcmt/issues?q=is%3Aissue+milestone%3Av3.2.2) | https://github.com/suzuki-shunsuke/tfcmt/compare/v3.2.1...v3.2.2 #### Features [#​288](https://togithub.com/suzuki-shunsuke/tfcmt/issues/288) (apply): Get the associated pull request with commit The behavior of getting notification destination (pull request or commit) in `tfcmt apply` is improved. ##### AS IS 1. Get pull request number from commit message 2. Get SHA from previous commit ##### TO BE 1. Get pull request number from associated pull request with GitHub API. https://docs.github.com/en/rest/commits/commits#list-pull-requests-associated-with-a-commit 2. Get SHA from current commit By getting associated pull request via GitHub API, this works even if the pull request was merged by squash merge. #### Others [#​279](https://togithub.com/suzuki-shunsuke/tfcmt/issues/279) Update Go to v1.18.1 [#​280](https://togithub.com/suzuki-shunsuke/tfcmt/issues/280) Update go-github to v43 [#​277](https://togithub.com/suzuki-shunsuke/tfcmt/issues/277) [#​278](https://togithub.com/suzuki-shunsuke/tfcmt/issues/278) [#​284](https://togithub.com/suzuki-shunsuke/tfcmt/issues/284) [#​287](https://togithub.com/suzuki-shunsuke/tfcmt/issues/287) Refactoring ### [`v3.2.1`](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.2.1) [Compare Source](https://togithub.com/suzuki-shunsuke/tfcmt/compare/v3.2.0...v3.2.1) [Pull Requests](https://togithub.com/suzuki-shunsuke/tfcmt/pulls?q=is%3Apr+milestone%3Av3.2.1) | [Issues](https://togithub.com/suzuki-shunsuke/tfcmt/issues?q=is%3Aissue+milestone%3Av3.2.1) | https://github.com/suzuki-shunsuke/tfcmt/compare/v3.2.0...v3.2.1 #### Bug Fixes [#​253](https://togithub.com/suzuki-shunsuke/tfcmt/issues/253) Fix the bug that comments of `tfcmt apply` patch comments of `tfcmt plan`. Follow up [#​245](https://togithub.com/suzuki-shunsuke/tfcmt/issues/245) Affected versions: [v3.2.0](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.2.1) ### [`v3.2.0`](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.2.0) [Compare Source](https://togithub.com/suzuki-shunsuke/tfcmt/compare/v3.1.1...v3.2.0) [Pull Requests](https://togithub.com/suzuki-shunsuke/tfcmt/pulls?q=is%3Apr+milestone%3Av3.2.0) | [Issues](https://togithub.com/suzuki-shunsuke/tfcmt/issues?q=is%3Aissue+milestone%3Av3.2.0) | https://github.com/suzuki-shunsuke/tfcmt/compare/v3.1.0...v3.2.0 ⚠️ This release includes a bug [#​253](https://togithub.com/suzuki-shunsuke/tfcmt/issues/253) . Please use [v3.2.1](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.2.1) or later. #### Features [#​199](https://togithub.com/suzuki-shunsuke/tfcmt/issues/199) [#​245](https://togithub.com/suzuki-shunsuke/tfcmt/issues/245) [#​248](https://togithub.com/suzuki-shunsuke/tfcmt/issues/248) [#​249](https://togithub.com/suzuki-shunsuke/tfcmt/issues/249) Support patching comments of `tfcmt plan` The option `-patch` has been added to `tfcmt plan` command. ```console tfcmt plan -patch -- terraform plan -no-color ``` And the configuration option `plan_patch` has also been added. ```yaml plan_patch: true ``` The command line option `-patch` takes precedence over configuration file option `plan_patch`. If you want to disable patching although `plan_patch` is true, please set `-patch=false`. ```console $ tfcmt plan -patch=false -- terraform plan -no-color ``` ##### Motivation By patching the comment instead of creating a new comment, you can keep the pull request comments clean. ##### Trouble shooting If the comment isn't patched expectedly, please set `-log-level=debug`. ```console $ tfcmt -log-level=debug plan -patch -- terraform plan -no-color ``` ##### ⚠️ Note to use tfcmt plan's patch option with github-comment hide If you hide comments by [github-comment hide](https://suzuki-shunsuke.github.io/github-comment/hide) and enable tfcmt plan's patch option, you should be careful not to hide tfcmt plan's comments. There are some ways to fix the problem. 1. Stop using `github-comment hide` 2. Fix github-comment hide's condition and exclude tfcmt's comments from the target ofgithub-comment hide 3. Run github-comment hide after tfcmt ### [`v3.1.1`](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v3.1.1) [Compare Source](https://togithub.com/suzuki-shunsuke/tfcmt/compare/v3.1.0...v3.1.1) [Pull Requests](https://togithub.com/suzuki-shunsuke/tfcmt/pulls?q=is%3Apr+milestone%3Av3.1.1) | [Issues](https://togithub.com/suzuki-shunsuke/tfcmt/issues?q=is%3Aissue+milestone%3Av3.1.1) | https://github.com/suzuki-shunsuke/tfcmt/compare/v3.1.0...v3.1.1 #### Bug Fixes [#​241](https://togithub.com/suzuki-shunsuke/tfcmt/issues/241) Fix not removing stale labels if there are too many labels in the pull request Thanks to [kyontan](https://togithub.com/kyontan). tfcmt sets a pull request label. When the result of `terraform plan` is changed, tfcmt removes an old label and sets a new label. But when the pull request has over 30 labels, tfcmt might not remove the old label. This change fixes the bug. #### Others [#​237](https://togithub.com/suzuki-shunsuke/tfcmt/issues/237) [#​238](https://togithub.com/suzuki-shunsuke/tfcmt/issues/238) [#​239](https://togithub.com/suzuki-shunsuke/tfcmt/issues/239) Move the document to GitHub Pages https://suzuki-shunsuke.github.io/tfcmt/

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.