-
-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0) #102
Open
renovate
wants to merge
1
commit into
release/v0
Choose a base branch
from
renovate/release/v0-cloudposse-s3-bucket-aws-4.x
base: release/v0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0) #102
renovate
wants to merge
1
commit into
release/v0
from
renovate/release/v0-cloudposse-s3-bucket-aws-4.x
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
renovate
bot
requested review from
jamengual and
joe-niland
and removed request for
a team
March 9, 2024 04:15
/terratest |
renovate
bot
changed the title
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Apr 14, 2024
renovate
bot
changed the title
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
May 3, 2024
renovate
bot
changed the title
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
May 9, 2024
renovate
bot
changed the title
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
May 20, 2024
renovate
bot
force-pushed
the
renovate/release/v0-cloudposse-s3-bucket-aws-4.x
branch
2 times, most recently
from
July 30, 2024 19:47
37d6741
to
3e4e3bf
Compare
renovate
bot
force-pushed
the
renovate/release/v0-cloudposse-s3-bucket-aws-4.x
branch
2 times, most recently
from
August 13, 2024 17:46
e382b77
to
67efe71
Compare
renovate
bot
changed the title
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Aug 14, 2024
renovate
bot
force-pushed
the
renovate/release/v0-cloudposse-s3-bucket-aws-4.x
branch
from
August 14, 2024 19:04
67efe71
to
3c79a78
Compare
renovate
bot
changed the title
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Aug 14, 2024
renovate
bot
changed the title
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Aug 28, 2024
renovate
bot
changed the title
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Sep 6, 2024
renovate
bot
force-pushed
the
renovate/release/v0-cloudposse-s3-bucket-aws-4.x
branch
from
September 24, 2024 18:12
3c79a78
to
88e90e8
Compare
renovate
bot
force-pushed
the
renovate/release/v0-cloudposse-s3-bucket-aws-4.x
branch
2 times, most recently
from
November 14, 2024 13:40
56c4e58
to
4f6c52d
Compare
renovate
bot
changed the title
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Dec 2, 2024
renovate
bot
changed the title
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Dec 11, 2024
renovate
bot
changed the title
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Dec 17, 2024
renovate
bot
changed the title
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Jan 1, 2025
renovate
bot
force-pushed
the
renovate/release/v0-cloudposse-s3-bucket-aws-4.x
branch
from
January 28, 2025 06:40
4f6c52d
to
e8f6bc1
Compare
renovate
bot
changed the title
chore(deps): update terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Update Terraform cloudposse/s3-bucket/aws to v4 (release/v0)
Jan 30, 2025
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:
3.0.0
->4.10.0
Release Notes
cloudposse/terraform-aws-s3-bucket (cloudposse/s3-bucket/aws)
v4.10.0
Compare Source
feat: Add filter_prefix, filter_suffix config options for queues and topics @vonZeppelin (#261)
what
Signed-off-by: Leonid Bogdanov <leonidbogdanov86@gmail.com>
references
v4.9.0
Compare Source
feat: add s3 request payment config @nitrocode (#259)
what
why
references
v4.8.0
Compare Source
feat: support eventbridge bucket notification @nitrocode (#255)
what
why
references
v4.7.3
Compare Source
🚀 Enhancements
fix: use new destination.bucket key in policy @nitrocode (#256)
what
why
destination_bucket
and newdestination.bucket
destination.bucket
and leftdestination_bucket
for backwards compatibility, as stated in variables.tf, and forgot to include the new value in the IAM policyreferences
🐛 Bug Fixes
fix: use new destination.bucket key in policy @nitrocode (#256)
what
why
destination_bucket
and newdestination.bucket
destination.bucket
and leftdestination_bucket
for backwards compatibility, as stated in variables.tf, and forgot to include the new value in the IAM policyreferences
v4.7.2
Compare Source
🚀 Enhancements
fix: correct bucket name to fix broken `-replication` role @amila-ku (#250)
what
why
references
v4.7.1
Compare Source
🚀 Enhancements
fix: s3 lambda event notification assignments @mpajuelofernandez (#253)
what
It seems there is a typo kind if error here
I think it should be
why
The S3 notification can not be created unless this is fixed
references
This should fix https://github.com/cloudposse/terraform-aws-s3-bucket/issues/252
🐛 Bug Fixes
fix: s3 lambda event notification assignments @mpajuelofernandez (#253)
what
It seems there is a typo kind if error here
I think it should be
why
The S3 notification can not be created unless this is fixed
references
This should fix https://github.com/cloudposse/terraform-aws-s3-bucket/issues/252
🤖 Automatic Updates
Update terratest to '>= 0.46.0' @osterman (#235)
what
>= 0.46.0
why
References
Migrate new test account @osterman (#248)
what
.github/settings.yml
.github/chatops.yml
fileswhy
.github/settings.yml
from org level to getterratest
environmenttest
accountReferences
Update .github/settings.yml @osterman (#247)
what
.github/settings.yml
.github/auto-release.yml
fileswhy
.github/settings.yml
from org levelreferences
Update .github/settings.yml @osterman (#246)
what
.github/settings.yml
.github/auto-release.yml
fileswhy
.github/settings.yml
from org levelreferences
v4.7.0
Compare Source
Make sure replica_kms_key_id is truly empty @stephan242 (#244)
references
closes #243
v4.6.0
Compare Source
Addition of S3 bucket event notification resource and Addition of S3 directory optional resource @mayank0202 (#240)
Issue - GH-239
what
This feature will make s3 event notifications which will have 3 options to trigger lambda or queue or topic so we can define a resource from this documentation.
aws_s3_bucket_notification
we also added s3 directory bucket which is a new feature in aws so addition of optional resource can be done if someone needs to use that with the help of terraform
aws_s3_directory_bucket
why
Enhanced Event-Driven Architecture: The introduction of S3 event notifications allows the S3 bucket to trigger Lambda functions, SQS queues, or SNS topics. This facilitates seamless integration with other AWS services and enables real-time processing of data, which is crucial for building event-driven architectures.
New AWS Feature Adoption: The addition of the aws_s3_directory_bucket resource reflects the latest AWS capabilities, ensuring that our infrastructure is up-to-date with current AWS offerings. This optional resource allows users to leverage new AWS features as they become available, promoting flexibility and future-proofing our Terraform configurations.
Improved Flexibility: By providing options to trigger different AWS services (Lambda, SQS, SNS), the solution becomes more versatile, catering to a wide range of use cases and workflows. This flexibility can lead to more efficient and effective data processing pipelines.
Reduced Operational Overhead: Automating responses to S3 events using Lambda functions, queues, or topics can significantly reduce manual intervention and operational overhead. This leads to improved efficiency and allows teams to focus on higher-value tasks.
references
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3\_bucket_notification
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3\_directory_bucket
https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html
v4.5.0
Compare Source
feat: Add missed tags @MaxymVlasov (#241)
what
Add tags to resources where they missed
v4.4.0
Compare Source
226: Add Expected Bucket Owner @houserx-ioannis (#238)
what
This PR addresses #226 about not being able to specify expected bucket owner in various S3 resources.
why
From AWS docs:
Because Amazon S3 identifies buckets based on their names, an application that uses an incorrect bucket name in a request could inadvertently perform operations against a different bucket than expected. To help avoid unintentional bucket interactions in situations like this, you can use bucket owner condition. Bucket owner condition enables you to verify that the target bucket is owned by the expected AWS account, providing an additional layer of assurance that your S3 operations are having the effects you intend.
references
#226
v4.3.0
Compare Source
Enforce the usage of modern TLS versions (1.2 or higher) for S3 connections @amontalban (#237)
what
This variables adds a policy to the bucket to deny connections that do not use TLS 1.2 or higher.
why
This is required by our security team.
references
https://repost.aws/knowledge-center/s3-enforce-modern-tls
🚀 Enhancements
Bump github.com/hashicorp/go-getter from 1.7.1 to 1.7.4 in /test/src @dependabot (#230)
Bumps github.com/hashicorp/go-getter from 1.7.1 to 1.7.4.
Release notes
Sourced from github.com/hashicorp/go-getter's releases.
Commits
268c11c
escape user provide string to git (#483)975961f
Merge pull request #433 from adrian-bl/netrc-fix0298a22
Merge pull request #459 from hashicorp/jbardin/setup-git-envc70d9c9
don't change GIT_SSH_COMMAND if there's no keyfile3d5770f
Merge pull request #458 from hashicorp/tsccr-auto-pinning/trusted/2023-09-180688979
Result of tsccr-helper -log-level=info -pin-all-workflows .e66f244
Merge pull request #454 from hashicorp/tsccr-auto-pinning/trusted/2023-09-11e80b3dc
Result of tsccr-helper -log-level=info -pin-all-workflows .2d49e24
Merge pull request #432 from hashicorp/tsccr-auto-pinning/trusted/2023-04-215ccb39a
Make addAuthFromNetrc ignore ENOTDIR errorsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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.
🤖 Automatic Updates
Bump github.com/hashicorp/go-getter from 1.7.1 to 1.7.4 in /test/src @dependabot (#230)
Bumps github.com/hashicorp/go-getter from 1.7.1 to 1.7.4.
Release notes
Sourced from github.com/hashicorp/go-getter's releases.
Commits
268c11c
escape user provide string to git (#483)975961f
Merge pull request #433 from adrian-bl/netrc-fix0298a22
Merge pull request #459 from hashicorp/jbardin/setup-git-envc70d9c9
don't change GIT_SSH_COMMAND if there's no keyfile3d5770f
Merge pull request #458 from hashicorp/tsccr-auto-pinning/trusted/2023-09-180688979
Result of tsccr-helper -log-level=info -pin-all-workflows .e66f244
Merge pull request #454 from hashicorp/tsccr-auto-pinning/trusted/2023-09-11e80b3dc
Result of tsccr-helper -log-level=info -pin-all-workflows .2d49e24
Merge pull request #432 from hashicorp/tsccr-auto-pinning/trusted/2023-04-215ccb39a
Make addAuthFromNetrc ignore ENOTDIR errorsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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.
Update release workflow to allow pull-requests: write @osterman (#234)
what
.github/workflows/release.yaml
) to have permission to comment on PRwhy
Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#233)
what
.github/workflows
) to use shared workflows from.github
repowhy
Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#232)
what
.github/workflows
) to addissue: write
permission needed by ReviewDogtflint
actionwhy
Update GitHub workflows @osterman (#231)
what
.github/workflows/settings.yaml
)why
Bump golang.org/x/net from 0.8.0 to 0.23.0 in /test/src @dependabot (#229)
Bumps golang.org/x/net from 0.8.0 to 0.23.0.
Commits
c48da13
http2: fix TestServerContinuationFlood flakes762b58d
http2: fix tipos in commentba87210
http2: close connections when receiving too many headersebc8168
all: fix some typos3678185
http2: make TestCanonicalHeaderCacheGrowth faster448c44f
http2: remove clientTesterc7877ac
http2: convert the remaining clientTester tests to testClientConnd8870b0
http2: use synthetic time in TestIdleConnTimeoutd73acff
http2: only set up deadline when Server.IdleTimeout is positive89f602b
http2: validate client/outgoing trailersDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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.
Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#227)
what
why
cldouposse/.github
repositoryAdd GitHub Settings @osterman (#221)
what
.github/settings.yaml
)why
Update README.md and docs @cloudpossebot (#218)
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 (#219)
what
make readme
to rebuildREADME.md
fromREADME.yaml
why
.github
repov4.2.0
Compare Source
Added IP-based statement in bucket policy @soya-miyoshi (#216)
what
source_ip_allow_list
variable.why
Use cases:
references
v4.1.0
Compare Source
🚀 Enhancements
fix: use for_each instead of count in aws_s3_bucket_logging @wadhah101 (#212)
what
Replaced the count with a for_each inside
aws_s3_bucket_logging.default
there's no point in the try since the type is clearly defined as list
why
When the
bucket_name
withinlogging
attribute is dynamically defined, like in the case of referencing a bucket created by terraform for loggingwe get this error
For each can work better in this case and will solve the previous error
references
🤖 Automatic Updates
Update README.md and docs @cloudpossebot (#214)
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 README.md and docs @cloudpossebot (#213)
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 README.md and docs @cloudpossebot (#209)
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
v4.0.1
Compare Source
🐛 Bug Fixes
Fix bug in setting dynamic `encryption_configuration` value @LawrenceWarren (#206)
what
s3_replication_rules.destination.encryption_configuration.replica_kms_key_id
set.why
There is a bug when trying to create an S3 bucket, which causes an error that stops the bucket being created
s3_replication_rules.destination.encryption_configuration.replica_kms_key_id
(newer)s3_replication_rules.destination.replica_kms_key_id
(older)This error is easily replicable by trying
compact(concat([try("string", "")], [try("string", "")]))[0]
in the Terraform console, which is a simplified version of the existing logic used aboveThe table below demonstrates the possible values of the existing code - you can see the outputs for value 2, value 3, and value 4 are not lists:
null
"string1"
null
"string1"
null
null
"string2"
"string2"
[]
"string1"
"string2"
"string1"
v4.0.0
Compare Source
Bug fixes and enhancements combined into a single breaking release @aknysh (#202)
Breaking Changes
Terraform version 1.3.0 or later is now required.
policy
input removedThe deprecated
policy
input has been removed. Usesource_policy_documents
instead.Convert from
to
Do not use list modifiers like
sort
,compact
, ordistinct
on the list, or it will trigger anError: Invalid count argument
. The length of the list must be known at plan time.Logging configuration converted to list
To fix #182, the
logging
input has been converted to a list. If you have a logging configuration, simply surround it with brackets.Replication rules brought into alignment with Terraform resource
Previously, the
s3_replication_rules
input had some deviations from the aws_s3_bucket_replication_configuration Terraform resource. Via the use of optional attributes, the input now closely matches the resource while providing backward compatibility, with a few exceptions.source_selection_criteria.sse_kms_encrypted_objects
was documented as an object with one member,enabled
, of typebool
. However, it only worked when set to thestring
"Enabled". It has been replaced with the resource's choice ofstatus
of type String.replication_time
. To enable Metrics without Replication Time Control, you must setreplication_time.status = "Disabled"
.These are not changes, just continued deviations from the resources:
existing_object_replication
cannot be set.token
to allow replication to be enabled on an Object Lock-enabled bucket cannot be set.what
local.source_policy_documents
and deprecated variablepolicy
(because of that, pump the module to a major version)lifecycle_configuration_rules
ands3_replication_rules
from loosely typed objects to fully typed objects with optional attributes.bucket_id
variablewhy
policy
was empty, meaning it had to be removed based on content, which would not be known at plan time if thepolicy
input was being generated.explanation
Any list manipulation functions should not be used in
count
since it can lead to the error:Using the local like this
would not work either if
var.policy
depends on apply-time resources from other TF modules.General rules:
When using
for_each
, the map keys have to be known at plan time (the map values are not required to be know at plan time)When using
count
, the length of the list must be know at plan time, the items inside the list are not. That does not mean that the list must be static with the length known in advance, the list can be dynamic and come from a remote state or data sources which Terraform evaluates first during plan, it just can’t come from other resources (which are only known after apply)When using
count
, no list manipulating functions can be used incount
- it will lead to theThe "count" value depends on resource attributes that cannot be determined until apply
error in some casesv3.1.3
Compare Source
Unfortunately, this change makes
count
unknown at plan time in certain situations. In general, you cannot use the output ofcompact()
incount
.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 @johncblandii (#201)
what
var.source_policy_documents
tolocal.source_policy_documents
sovar.policy
usage was still supportedwhy
var,source_policy_documents
sovar.policy
being combined withvar.source_policy_documents
intolocal.source_policy_documents
does not providetrue
for the ternary to executereferences
v3.1.2
: Fix Public Bucket CreationCompare Source
What's Changed
New Contributors
Full Changelog: cloudposse/terraform-aws-s3-bucket@3.1.1...3.1.2
v3.1.1
Compare Source
🐛 Bug Fixes
Revert change to Transfer Acceleration from #178 @Nuru (#180)
what
why
v3.1.0
: Support new AWS S3 defaults (ACL prohibited)Compare Source
Note: this version introduced drift detection and correction for Transfer Acceleration. Unfortunately, that change prevents deployment of buckets in regions that do not support Transfer Acceleration. Version 3.1.1 reverts that change so that S3 buckets can be deployed by this module in all regions. It does, however, mean that when
var.transfer_acceleration_enabled
isfalse
, Terraform does not track or revert changes to Transfer Acceleration made outside of this module.Make compatible with new S3 defaults. Add user permissions boundary. @Nuru (#178)
what
aws_s3_bucket_accelerate_configuration
andaws_s3_bucket_versioning
resources even when the feature is disabled, to enable drift detectionwhy
references
Always include `aws_s3_bucket_versioning` resource @mviamari (#172)
what
aws_s3_bucket_versioning
resource to track changes made to bucket versioning configurationwhy
aws_s3_bucket_versioning
, the expectation is that the bucket versioning is disabled/suspend for the bucket. If bucket versioning is turned on outside of terraform (e.g. through the console), the change is not detected by terraform unless theaws_s3_bucket_versioning
resource exists.references
Add support for permission boundaries on replication IAM role @mchristopher (#170)
what
why
references
🤖 Automatic Updates
Update README.md and docs @cloudpossebot (#164)
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: 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 becomes conflicted, 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.