chore(deps): update dependency gruntwork-io/terragrunt to v0.37.1 (terragrunt/dockerfile) (master) #413
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.
This PR contains the following updates:
0.36.8
->0.37.1
Release Notes
gruntwork-io/terragrunt
v0.37.1
Compare Source
Description
This release is functionally equivalent to v0.37.0
Update the documentation to suggest
generate
blocks for managing the remote state backend configuration for users who do not want automated state management by Terragrunt.v0.37.0
Compare Source
Updated CLI args, config attributes and blocks
remote_state
[BACKWARD INCOMPATIBLE]Description
Updated logic for handling
remote_state
to enforce what is defined in the block of config, the change affects default encryption settings, public access blocking, bucket policy (enforce SSL only), access logging, and versioningFixed behavior for enforcing
EnforcedTLS
to not overwrite already configuredRootAccess
policyMigration guide
If you do not want
terragrunt
to update the S3 bucket based on the configurations, you can define the config attributedisable_bucket_update = true
in theremote_state
block.If you have an environment where it is difficult to update
terragrunt
and your configuration simultaneously, you can use v0.36.12 which supports the newdisable_bucket_update
configuration, but does not implement the bucket updating behavior.To perform a safe upgrade:
v0.36.12
disable_bucket_update = true
in theremote_state
blockconfig
map.terragrunt
to confirm Terragrunt doesn't update the state buckets.v0.37.0
and confirm Terragrunt still does not update the state buckets.Special thanks
Special thanks to the following users for their contribution!
Related links
v0.36.12
Compare Source
Updated CLI args, config attributes and blocks
remote_state
Description
disable_bucket_update
configuration to theremote_state
block for the S3 backend. This flag has no functional effect, but is useful to ease the transition tov0.37.0
. Refer to the release notes for v0.37.0 for more details.Related links
v0.36.11
Compare Source
Description
Upgraded
go-getter
dependency to 1.5.11 with CVE-2022-29810 fixesSpecial thanks
Special thanks to @dependabot for their contribution!
Related links
v0.36.10
Compare Source
Description
--terragrunt-strict-validate
ignored unused input variablesSpecial thanks
Special thanks to the following users for their contribution!
Related links
v0.36.9
Compare Source
Description
git rev-parse --show-toplevel
to pass environment variablesSpecial Thanks
References
https://github.com/gruntwork-io/terragrunt/pull/2086
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.