Allow v0.36 to define disable_bucket_update to make it easier to transition to v0.37 #2105
+73
−0
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
yorinasub17
requested review from
rhoboat,
zackproser and
denis256
as code owners
denis256
approved these changes
May 13, 2022
|
Thanks for review! Will merge this in, and then cut 0.36.12 |
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.
IMPORTANT: Merges into v036-dev, which is a snapshot of v0.36.11
This PR is intended to be a patch release for
v0.36.xthat is intended to smooth the upgrade process from v0.36 to v0.37. Right now, users can't prepare for the v0.37 update by preconfiguring their terragrunt project withdisable_bucket_update = true, becauseterragrunt0.36.11 doesn't support this config (terragrunt crashes if that is set).In this PR, we add the config variable but do nothing with it so that users can setup for the v0.37 update.
When this is merged to
v036-dev, I'll go ahead and cut a patch releasev0.36.12pointing to that branch, and then will delete the branches.