chore(deps): update terraform cloudposse/s3-log-storage/aws to v2.1.0 (main) - #165
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update terraform cloudposse/s3-log-storage/aws to v2.1.0 (main)#165renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
requested review from
Jeremy White (dudymas),
PePe Amengual (jamengual) and
Erik Osterman (Cloud Posse) (osterman)
September 8, 2026 23:35
|
/terratest |
This file contains hidden or 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
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.
This PR contains the following updates:
2.0.0→2.1.0Release Notes
cloudposse/terraform-aws-s3-log-storage (cloudposse/s3-log-storage/aws)
v2.1.0Compare Source
✨ Features
feat: add object_lock_enabled passthrough @Benbentwo (#141)
what
cloudposse/s3-bucket/awsfrom4.10.0to4.15.0.object_lock_enabledinput as a variable on this module.>= 4.9.0to>= 6.37.0, whichs3-bucket4.15.0 requires.why
object_lock_configurationis the only Object Lock knob this module exposes, and it is a bucket-wide default retentionrule — mode plus days or years, both required. There is no way to ask for "Object Lock enabled, nothing locked by
default", which is what you want when objects are protected individually with a retention period or a legal hold.
That matters for log buckets specifically. A default retention rule interacts badly with lifecycle expiration: S3 cannot
delete an object still under retention, so a retention period longer than the expiration deadlocks the lifecycle rule.
Callers who want the WORM capability without that coupling currently have no option.
cloudposse/terraform-aws-s3-bucketalready solved this inv4.15.0 by adding a bare
object_lock_enabledbool alongsideobject_lock_configuration. This PR just carries that input up one layer. Thevariable description is copied verbatim from the child module so the two stay consistent.
references
object_lock_enabledincloudposse/terraform-aws-s3-bucketv4.15.0note on the provider floor
The provider bump is the part worth a second look — it comes along with
s3-bucket4.15.0 rather than from this changeitself, and it is a large jump for consumers still on provider v4 or v5. Happy to split it out or gate it differently if
you would rather land the passthrough separately.
🤖 Automatic Updates
chore(deps): bump github.com/ulikunitz/xz from 0.5.10 to 0.5.14 in /test/src @[dependabot[bot]](https://redirect.github.com/apps/dependabot) (#131)
Bumps [github.com/ulikunitz/xz](https://redirect.github.com/ulikunitz/xz) from 0.5.10 to 0.5.14.Commits
7184815Preparation of release v0.5.1488ddf1dAddress Security Issue GHSA-jc7w-c686-c4v9c8314b8Add new package xio with WriteCloserStack4f11dceUpdate README.md and SECURITY.md to address security questionsf56ebbfTODO.md: fix a typo9d122a6release version v0.5.114ce6f08lzma: fix handling of small dictionary sizes0b7c695xz: add reader benchmark5535077xz: add compression reate to Writer benchmark886dc9axz: add benchmark for WriterYou can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.
Configuration
📅 Schedule: (UTC)
🚦 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.