Skip to content

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

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

chore(deps): update terraform cloudposse/s3-log-storage/aws to v2#117
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/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.22.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

v1.4.5

Compare Source

🚀 Enhancements
fix: remove join calls on bucket arn + id usage @​carterdanko-dw (#​125)
what
  • Initially put the wrong values for coditions, just needs to be a list
  • Bucket should be single resource vs joining on a list.
references

issue #122

🐛 Bug Fixes
fix: remove join calls on bucket arn + id usage @​carterdanko-dw (#​125)
what
  • Initially put the wrong values for coditions, just needs to be a list
  • Bucket should be single resource vs joining on a list.
references

issue #122

v1.4.4

Compare Source

🚀 Enhancements
Issue-122/Values expect list of strings vs string @​carterdanko-dw (#​123)
what

Updating the sqs iam permissions, as the values expects to be a list of strings vs just the single string arn that is the output of the module.

why

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document#condition-1 expects to be a list of strings, vs just the single string arn of the s3 bucket.

references

Github issue #​122

🐛 Bug Fixes
Issue-122/Values expect list of strings vs string @​carterdanko-dw (#​123)
what

Updating the sqs iam permissions, as the values expects to be a list of strings vs just the single string arn that is the output of the module.

why

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document#condition-1 expects to be a list of strings, vs just the single string arn of the s3 bucket.

references

Github issue #​122

🤖 Automatic Updates
Migrate new test account @​osterman (#​119)
what
  • Update .github/settings.yml
  • Update .github/chatops.yml files
why
  • Re-apply .github/settings.yml from org level to get terratest environment
  • Migrate to new test account
References
  • DEV-388 Automate clean up of test account in new organization
  • DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
  • DEV-386 Update terratest to use new testing account with GitHub OIDC
Update .github/settings.yml @​osterman (#​118)
what
  • Update .github/settings.yml
  • Drop .github/auto-release.yml files
why
  • Re-apply .github/settings.yml from org level
  • Use organization level auto-release settings
references
  • DEV-1242 Add protected tags with Repository Rulesets on GitHub
Update .github/settings.yml @​osterman (#​112)
what
  • Update .github/settings.yml
  • Drop .github/auto-release.yml files
why
  • Re-apply .github/settings.yml from org level
  • Use organization level auto-release settings
references
  • DEV-1242 Add protected tags with Repository Rulesets on GitHub
Update .github/settings.yml @​osterman (#​111)
what
  • Update .github/settings.yml
  • Drop .github/auto-release.yml files
why
  • Re-apply .github/settings.yml from org level
  • Use organization level auto-release settings
references
  • DEV-1242 Add protected tags with Repository Rulesets on GitHub
Update release workflow to allow pull-requests: write @​osterman (#​110)
what
  • Update workflow (.github/workflows/release.yaml) to have permission to comment on PR
why
  • So we can support commenting on PRs with a link to the release
Update GitHub Workflows to use shared workflows from '.github' repo @​osterman (#​109)
what
  • Update workflows (.github/workflows) to use shared workflows from .github repo
why
  • Reduce nested levels of reusable workflows
Update GitHub Workflows to Fix ReviewDog TFLint Action @​osterman (#​108)
what
  • Update workflows (.github/workflows) to add issue: write permission needed by ReviewDog tflint action
why
  • The ReviewDog action will comment with line-level suggestions based on linting failures
Update GitHub workflows @​osterman (#​107)
what
  • Update workflows (.github/workflows/settings.yaml)
why
  • Support new readme generation workflow.
  • Generate banners
Use GitHub Action Workflows from `cloudposse/.github` Repo @​osterman (#​106)
what
  • Install latest GitHub Action Workflows
why
  • Use shared workflows from cldouposse/.github repository
  • Simplify management of workflows from centralized hub of configuration
Add GitHub Settings @​osterman (#​104)
what
  • Install a repository config (.github/settings.yaml)
why
  • Programmatically manage GitHub repo settings
Update README.md and docs @​cloudpossebot (#​99)
what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

Update Scaffolding @​osterman (#​100)
what
  • Reran make readme to rebuild README.md from README.yaml
  • Migrate to square badges
  • Add scaffolding for repo settings and Mergify
why
  • Upstream template changed in the .github repo
  • Work better with repository rulesets
  • Modernize look & feel

v1.4.3

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/s3-bucket/aws to v3.1.3 (main) @​renovate (#​95)

This PR contains the following updates:

Package Type Update Change
cloudposse/s3-bucket/aws (source) module patch 3.1.2 -> 3.1.3

Release Notes
cloudposse/terraform-aws-s3-bucket (cloudposse/s3-bucket/aws)
v3.1.3

Compare Source

Unfortunately, this change makes count unknown at plan time in certain situations. In general, you cannot use the output of compact() in count.

The solution is to stop using the deprecated policy input and revert to 3.1.2 or upgrade to 4.0.

🚀 Enhancements
Fix `source_policy_documents` combined with `var.policy` being ignored @​&#​8203;johncblandii (#&#​8203;201)
what
  • Changed var.source_policy_documents to local.source_policy_documents so var.policy usage was still supported
why
  • The ternary check uses var,source_policy_documents so var.policy being combined with var.source_policy_documents into local.source_policy_documents does not provide true for the ternary to execute
references

Update README.md and docs @​cloudpossebot (#​94)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates


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:52
@mergify

mergify Bot commented Aug 25, 2025

Copy link
Copy Markdown

/terratest

@renovate
renovate Bot force-pushed the renovate/cloudposse-s3-log-storage-aws-2.x branch from 86fb220 to d380e3d Compare September 8, 2026 23:39
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