fix(infra): cap Google provider below 8.0.0 and update to 7.46.0 - #2809
Closed
jcscottiii wants to merge 1 commit into
Closed
fix(infra): cap Google provider below 8.0.0 and update to 7.46.0#2809jcscottiii wants to merge 1 commit into
jcscottiii wants to merge 1 commit into
Conversation
Cap hashicorp/google provider version to < 8.0.0, update provider to latest 7.x release (7.46.0), and configure Dependabot to ignore major updates for Terraform. ## Context & Root Cause PR #2804 was opened by Dependabot titled 'bump hashicorp/google from 7.44.0 to 7.45.0' (labeled version-update:semver-minor), but committed provider version 8.0.0 into infra/.terraform.lock.hcl due to an unbounded constraint (>= 5.4.0) in infra/providers.tf. Upon merging, post-merge Cloud Build failed with GCP API error 400 because Google provider 8.0.0 changed the default load_balancing_scheme in backend services and forwarding rules from EXTERNAL to EXTERNAL_MANAGED, which GCP disallows in-place on active Classic ALBs without a multi-phase migration workflow. ## Changes - infra/providers.tf: Restrict hashicorp/google version constraint to '>= 5.4.0, < 8.0.0' and add reference comment to #2808. - .github/dependabot.yml: Ignore version-update:semver-major for hashicorp/google in /infra. - infra/.terraform.lock.hcl: Lock hashicorp/google to 7.46.0 (latest 7.x release). Fixes #2807 Refs #2808
Collaborator
Author
|
Superseded: Provider 8.0.0 had already migrated state attributes (such as google_secret_manager_secret_version.otel_config_version) on staging during PR #2804, causing provider 7.x to fail decoding the remote state with 'Resource instance managed by newer provider version'. Opening a new PR that retains provider 8.0.0 and explicitly declares load_balancing_scheme = "EXTERNAL" to safely unblock deployments. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Cap
hashicorp/googleprovider version to< 8.0.0, update provider to latest 7.x release (7.46.0), and configure Dependabot to ignore major updates for Terraform.Context & Root Cause
PR #2804 was opened by Dependabot titled
bump hashicorp/google from 7.44.0 to 7.45.0(labeledversion-update:semver-minor), but committed provider version8.0.0intoinfra/.terraform.lock.hcldue to an unbounded constraint (>= 5.4.0) ininfra/providers.tf.Upon merging, post-merge Cloud Build failed with GCP API error 400 because Google provider 8.0.0 changed the default
load_balancing_schemein backend services and forwarding rules fromEXTERNALtoEXTERNAL_MANAGED, which GCP disallows in-place on active Classic ALBs without a multi-phase migration workflow.Changes
Fixes #2807
Refs #2808