Skip to content

chore(deps): update terraform cloudposse/s3-log-storage/aws to v2 (main) - #355

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/main-cloudposse-s3-log-storage-aws-2.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/main-cloudposse-s3-log-storage-aws-2.x

Conversation

@renovate

@renovate renovate Bot commented Aug 25, 2025 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
cloudposse/s3-log-storage/aws (source) module major 1.4.5 → 2.1.0

Release Notes

cloudposse/terraform-aws-s3-log-storage (cloudposse/s3-log-storage/aws)

v2.1.0

Compare Source

✨ Features

feat: add object_lock_enabled passthrough @​Benbentwo (#​141)

what

  • Bump cloudposse/s3-bucket/aws from 4.10.0 to 4.15.0.
  • Expose that module's object_lock_enabled input as a variable on this module.
  • Raise the AWS provider floor from >= 4.9.0 to >= 6.37.0, which s3-bucket 4.15.0 requires.

why

object_lock_configuration is the only Object Lock knob this module exposes, and it is a bucket-wide default retention
rule
— 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-bucket already solved this in
v4.15.0 by adding a bare
object_lock_enabled bool alongside object_lock_configuration. This PR just carries that input up one layer. The
variable description is copied verbatim from the child module so the two stay consistent.

references

note on the provider floor

The provider bump is the part worth a second look — it comes along with s3-bucket 4.15.0 rather than from this change
itself, 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

Dependabot compatibility score

You 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will 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.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

v2.0.0

Compare Source

Two errors when trying to plan 'Invalid count argument' and 'Incorrect attribute value type' @​goruha (#​121)

what

  • Fix
│ Error: Invalid count argument
│
│   on .terraform\modules\foo.vpc_flow_logs.s3_log_storage_bucket.aws_s3_bucket\main.tf line 64, in resource "aws_s3_bucket_logging" "default":
│   64:   count  = local.enabled && var.logging != null ? 1 : 0
│
│ The "count" value depends on resource attributes that cannot be determined until
│ apply, so Terraform cannot predict how many instances will be created. To work
│ around this, use the -target argument to first apply only the resources that the
│ count depends on.
╵

references

🤖 Automatic Updates

Fix go version in tests @​osterman (#​127)

what

  • Update go 1.24

why

  • Error loading shared library libresolv.so.2 in Go 1.20

References

Replace Makefile with atmos.yaml @​osterman (#​126)

what

  • Remove Makefile
  • Add atmos.yaml

why

  • Replace build-harness with atmos for readme genration

References

  • DEV-3229 Migrate from build-harness to atmos

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the auto-update This PR was automatically generated label Aug 25, 2025
@renovate
renovate Bot requested review from a team as code owners August 25, 2025 19:24
@coderabbitai

coderabbitai Bot commented Aug 25, 2025 •

Copy link
Copy Markdown

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (3)
  • Bump
  • chore(deps)
  • WIP

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

@mergify

mergify Bot commented Aug 25, 2025

Copy link
Copy Markdown

/terratest

@renovate
renovate Bot force-pushed the renovate/main-cloudposse-s3-log-storage-aws-2.x branch 2 times, most recently from 695e018 to 31eed4e Compare October 1, 2025 04:16
@renovate
renovate Bot force-pushed the renovate/main-cloudposse-s3-log-storage-aws-2.x branch from 31eed4e to a56e4f5 Compare October 23, 2025 15:43
@renovate
renovate Bot force-pushed the renovate/main-cloudposse-s3-log-storage-aws-2.x branch from a56e4f5 to 2e22f68 Compare December 5, 2025 23:25
@renovate
renovate Bot force-pushed the renovate/main-cloudposse-s3-log-storage-aws-2.x branch 2 times, most recently from b8a32a3 to b1eb772 Compare January 16, 2026 12:39
@renovate
renovate Bot force-pushed the renovate/main-cloudposse-s3-log-storage-aws-2.x branch 2 times, most recently from 90b990e to 385b723 Compare February 19, 2026 20:21
@renovate
renovate Bot force-pushed the renovate/main-cloudposse-s3-log-storage-aws-2.x branch from 385b723 to e485f14 Compare February 27, 2026 01:16
@renovate
renovate Bot force-pushed the renovate/main-cloudposse-s3-log-storage-aws-2.x branch 2 times, most recently from e4d8d62 to d4a69ec Compare May 20, 2026 13:07
@renovate
renovate Bot force-pushed the renovate/main-cloudposse-s3-log-storage-aws-2.x branch 2 times, most recently from 18cd3e8 to c011214 Compare August 12, 2026 21:32
@renovate
renovate Bot force-pushed the renovate/main-cloudposse-s3-log-storage-aws-2.x branch from c011214 to 783e29a Compare September 8, 2026 23:28

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-update This PR was automatically generated

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants