fix: bump terraform base version from 1.3.0 to 1.3.10 #1253
Conversation
This file contains 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
caetano-colin
changed the title
caetano-colin
requested review from
rjerrems,
gtsorbo,
eeaton and
a team
as code owners
|
i've been running this project on 1.7.4 without issues, we could probably upgrade even further. |
|
/gcbrun |
eeaton
approved these changes
May 28, 2024
fmichaelobrien
approved these changes
May 28, 2024
There was a problem hiding this comment.
/lgtm
Note: I have been running a full LZ deploy using terraform 1.3.10 override for the last couple deploys - all is good - as expected
GoogleCloudPlatform/pbmm-on-gcp-onboarding#360
The 0-bootstrap step should be run with 1.3.10 and not 1.5+ or a statefile sync issue will occur in 1-org when we kick in the CB trigger that runs the 1.3.10 container
|
reference: #1151 |
This was referenced May 28, 2024
|
/gcbrun |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Because of the issue described in this link:
hashicorp/terraform#34014
Some users may experience this error:
This can easily be fixed by upgrading the version to 1.3.10 when using terraform 1.3 series