Skip to content

Conversation

@nika-pr
Copy link

@nika-pr nika-pr commented Nov 5, 2025

Since nobody is looking to fix PR #535, this is my attempt to get the dependencies finally updated.

@nika-pr nika-pr requested review from a team, ayushmjain, imrannayer and q2w as code owners November 5, 2025 07:30
@nika-pr nika-pr changed the title feat(deps): Update Terraform Google Provider to v7 feat(deps): Update Terraform Google Provider to v7 (major) Nov 5, 2025
@rjw57
Copy link

rjw57 commented Nov 5, 2025

Firstly, thanks @nika-pr for moving this forward as I'm sure there are many of us poor souls blocked from moving to provider v7 because of this. (For us, University of Cambridge DevOps, this is blocking updates for around 40 different terraform-driven deployments.)

I wonder if this PR may even be bolder by removing the < 8 restriction from the provider version and only define a minimum version? X-posting my observation from #538: terraform's best practice guide for version requirements recommends that reusable modules only specify a minimum version requirement:

Reusable modules should constrain only their minimum allowed versions of Terraform and providers, such as >= 0.12.0. This helps avoid known incompatibilities, while allowing the user of the module flexibility to upgrade to newer versions of Terraform without altering the module.

(my emphasis)

@nika-pr nika-pr changed the title feat(deps): Update Terraform Google Provider to v7 (major) feat(deps): Raise upper Terraform Google Provider bound to v8 Nov 5, 2025
@apeabody
Copy link
Contributor

apeabody commented Nov 5, 2025

/gcbrun

@imrannayer
Copy link
Collaborator

fixed in #556

@imrannayer imrannayer closed this Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants