Renovatebot has updated the test matrix to only test google provider >= 6.0 which was not the original plan. The idea was that we would test multiple major versions of the google provider as we want to support all of our boilerplates which could be running version's 4.x, 5.x, or 6.x currently.
We need to unpick this and get back to running tests against these three versions of the provider.
Tagging @dkh21 for visibility as they merged the Renovatebot MR. Apologies, got confused, MR was merged by @rh841.
Edited
Designs
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related or that one is blocking others.
Learn more.
In other words, it will not work with google providers 4.x and 5.x.
4.x and 5.x jobs will fail with obvious error
│ Error: Failed to query available provider packages│ │ Could not retrieve the list of available versions for provider│ hashicorp/google: no available releases match the given constraints >=│ 3.54.0, > 4.0.0, >= 4.0.0, < 5.0.0, >= 6.0.0, >= 6.1.0, < 7.0.0
Version rollback will not help with this, because, for example v9 (version that was updated in mentioned commit) of the serverless_negs module has = 4.50, < 5.0 , that means it will not work with v6 provider.
Yeah, this is exactly the issue that this test matrix was supposed to catch. We have many infrastructure projects which use this module but are configured to use google provider 4.x. I wanted to try and support those projects for as long as possible, however, now that we have bumped the serverless_negs and sql modules to their latest versions we are forced to make this module >= 6 which in turn forces the dependant infrastructure repos to update their google module version. I guess this is just how we will have to do things with renovate bot updating everything automatically for us, but ideally I was trying to keep this module's version constraint wide enough that it could be used across most/many of our infra repos.
I'm happy to close this off and see how it goes. If no projects complain when they update then that is fine I guess - and we all agree that keeping our versions up to date is a good thing so maybe use forcing it with this module's version constraint is not the end of the world.