Update Terraform github to v6.8.0#182
Conversation
GitLab Pipeline ActionGeneral informationLink to pipeline: https://gitlab.com/code0-tech/infrastructure/mensa/-/pipelines/2155824189 Status: Passed Job summariestf-plan:server_administrationNo changes. Your infrastructure matches the configuration. tf-plan:githubNo changes. Your infrastructure matches the configuration. tf-plan:mainNo changes. Your infrastructure matches the configuration. |
c8ec068 to
7ed4738
Compare
7cc77f9 to
fb956cf
Compare
2f737ae to
0993abd
Compare
0993abd to
705339d
Compare
|
There have been quite a few bugs in the last versions and I already see an issue in their repository for this version for a resource that we use. Closing to not take the risk |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
6.7.1->6.8.0Release Notes
integrations/terraform-provider-github (github)
v6.8.0Compare Source
What's Changed
🚀 New Features
🐛 Bugfixes
🛠️ Maintenance
📝 Documentation
New Contributors
Full Changelog: integrations/terraform-provider-github@v6.7.0...v6.8.0
v6.7.5Compare Source
[fix]: v6.7.4 causes Internal validation error during TF Init #2855
Full Changelog: integrations/terraform-provider-github@v6.7.4...v6.7.5
v6.7.4Compare Source
v6.7.4
This patch appropriately handles the cases when a Terraform resource has an Update function defined (which was recently added), the Terraform SDK requires that any field that can change must either have
ForceNew: true(meaning changes require resource recreation) or for that field to be a computed-only field.The
destroy_on_driftfield is a provider config setting that controls how drift detection works - it's not a field that maps to the GitHub API. When implementations try to change this field Terraform will execute the plan properly but fail on the apply because the Update function didn't know how to handle the destroy_on_drift change.Lastly reads now handle setting
encrypted_valueandplaintext_valueto nil to trigger an update when the "stored" update dates do not match.Full Changelog: integrations/terraform-provider-github@v6.7.3...v6.7.4
v6.7.3Compare Source
v6.7.3
This patch addresses the issue where the Update function was missed during the cherry pick for
github_actions_secretresource.Tests were also added to avoid regressions in the future.
Full Changelog: integrations/terraform-provider-github@v6.7.2...v6.7.3
v6.7.2Compare Source
v6.7.2
Note: This patch contains the addition of the
destroy_on_driftproperty togithub_actions_secretresource because the exact same issue was present there as well.Bug Fixes
Fixed drift detection bug that caused "Provider produced inconsistent result" errors in github_actions_organization_secret and github_actions_secret resources. The bug occurred when secrets were modified externally - the timestamp wasn't being updated after drift detection, causing infinite loops of false positive drift detection. | #2832
Features
Added destroy_on_drift property to github_actions_secret resource (repository-level secrets), and matches the functionality already available in github_actions_organization_secret. Also includes proper schema migration from v0 to v1 and ensures the property defaults to true for backward compatibility. | #2832
Full Changelog: integrations/terraform-provider-github@v6.7.1...v6.7.2
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 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.