Update Terraform github.com/cloudposse/terraform-aws-s3-log-storage to v0.28.3 (main) #17
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:
tags/0.1.3
->0.28.3
Release Notes
cloudposse/terraform-aws-s3-log-storage (github.com/cloudposse/terraform-aws-s3-log-storage)
v0.28.3
: Not recommended, use v0.26.0 or v1.x insteadCompare Source
Update: This version no longer recommended
With the release of version 1.0.0 of this module, use of this version is no longer recommended. When you are able to use Terraform v1.3.0 or later and Terraform AWS provider v4.9.0 or later, upgrade directly to v1.0.0 or later of this module.
🤖 Automatic Updates
Update Terraform cloudposse/s3-bucket/aws to v3 @renovate (#78)
This PR contains the following updates:
2.0.1
->3.0.0
v0.28.2
: Action required if updating from prior to v0.28.0Compare Source
Update: This version no longer recommended
With the release of version 1.0.0 of this module, use of this version is no longer recommended. When you are able to use Terraform v1.3.0 or later and Terraform AWS provider v4.9.0 or later, upgrade directly to v1.0.0 or later of this module.
v0.28.0 introduced breaking changes with high risk of permanent data loss. See release notes there. This is only a safe upgrade if upgrading from v0.28.0.
We will convert to semantic versioning (incrementing the major version number for breaking changes), but having missed the opportunity to do that for earlier versions of this module, we are waiting for the next major change, expected to be soon after Terraform v1.3 is released.
🤖 Automatic Updates
Update Terraform cloudposse/s3-bucket/aws to v2.0.1 @renovate (#76)
This PR contains the following updates:
2.0.0
->2.0.1
v0.28.1
: accidental release, do not useCompare Source
v0.28.0 introduced breaking changes with high risk of permanent data loss. See release notes there. This is only a safe upgrade if upgrading from v0.28.0.
We will convert to semantic versioning (incrementing the major version number for breaking changes), but having missed the opportunity to do that for earlier versions of this module, we are waiting for the next major change, expected to be soon after Terraform v1.3 is released.
git.io->cloudposse.tools update @dylanbannon (#73)
what and why
Change all references to
git.io/build-harness
intocloudposse.tools/build-harness
, sincegit.io
redirects will stop working on April 29th, 2022.References
🤖 Automatic Updates
Update Terraform cloudposse/s3-bucket/aws to v2 @renovate (#72)
This PR contains the following updates:
0.49.0
->2.0.3
v0.28.0
: (Action Needed) Support AWS v4 providerCompare Source
WARNING, DATA LOSS LIKELY if you do not follow upgrade instructions:
🚀 Enhancements
Support AWS v4 provider @Nuru (#71)
what
null-label
force_destroy_enabled
why
references
v0.27.0
: (WARNING: Potential Data Loss) Prepare for AWS provider v4Compare Source
Update: This version no longer recommended
With the release of version 1.0.0 of this module, use of this version is no longer recommended. When you are able to use Terraform v1.3.0 or later and Terraform AWS provider v4.9.0 or later, upgrade directly to v1.0.0 or later of this module.
Warning: Potential total data loss
This release is a refactoring in preparation for supporting Terraform AWS Provider v4. One feature was removed, but otherwise there are no changes to inputs or behavior. However, the Terraform "addresses" of resources have changed, so you are need to run several
terraform state mv
commands.Warning: failure to run the required
terraform state mv
commands will cause Terraform to delete your existing S3 bucket and create a new one, deleting all the data stored in the bucket in the process.Details on how to safely upgrade are in this repository's Wiki here
Support for "MFA delete" removed
In #54 a contributor added support for MFA delete via the
versioning_mfa_delete_enabled
. In AWS provider version 3.x this argument was documented with the caveatWith AWS provider version 4.0, this argument now does toggle the setting. Unfortunately, that adds the requirement then when it is enabled, you must supply a current MFA token every time you run
terraform apply
. That is not compatible with automation, and therefore we have no intention to support it and have removed theversioning_mfa_delete_enabled
input.🚀 Enhancements
Refactor to use s3-bucket module, update in general @Nuru (#66)
what
mfa_delete
< 4.0
and disable Renovate bot, closes #64why
mfa_delete
enabled requires entering an MFA token for every Terraform operation, which is incompatible with automation. Users requiringmfa_delete
should either not use Terraform or create their own fork.notes
This is the first of 2 upgrade releases to get this module to support Terraform AWS Provider v4. We are breaking it into 2 releases so that users have the option of upgrading step-by-step rather than all at once. Upgrade instructions are here.
Cleanups and safety checks for upgrade @Nuru (#70)
what
force_destroy
istrue
why
force_destroy
istrue
then an automated, unattended process could cause the S3 bucket to be deleted and all data in it irretrievably lostreferences
Closes Renovate PRs:
build-harness
)v0.26.0
: Latest recommended v0 releaseCompare Source
This is the latest recommended v0.x version to use.
If this version does not meet your needs, please switch to version 1.x, and review the release notes for v1.0.0 for guidance on the differences.
Changes in this release
Add S3 bucket ownership controls @max-lobur (#61)
what
why
bucket-owner-full-control
ACL is specified, the bucket account take ownership, otherwise the writer account keeps ownership. Bucket on its side may enforce presence of thebucket-owner-full-control
ACL which we already do when needed. So this setting was the only missing piece to make ownership work like we expectedObjectWriter
. It corresponds to legacy S3 behavior which was broken for us. Decided to always set toBucketOwnerPreferred
and not allow to customize. If the owner must be preserved, we should not passbucket-owner-full-control
- this is a more clear way to control the behavior.references
v0.25.0
Compare Source
Add support for bucket notifications @max-lobur (#60)
what
why
v0.24.1
Compare Source
🤖 Automatic Updates
Update context.tf @cloudpossebot (#59)
what
This is an auto-generated PR that updates the
context.tf
file to the latest version fromcloudposse/terraform-null-label
why
To support all the features of the
context
interface.v0.24.0
Compare Source
Add variable access_log_bucket_prefix to customize S3 access log configuration @adamantike (#57)
What
Allow changing the prefix to be used in the specified S3 bucket for access logs.
Maintain current prefix as default value, for backwards compatibility.
Why
This is useful for projects using different standards (e.g. path with bucket name in the root folder).
v0.23.0
Compare Source
add allow_ssl_requests_only flag @mcalhoun (#56)
what
why
data "aws_partition"
v0.22.0
Compare Source
add allow_ssl_requests_only flag @mcalhoun (#55)
what
allow_ssl_requests_only
flag to force the bucket to be accessed via TLS onlywhy
references
v0.21.0
Compare Source
added versioning mfa delete enabled option @chafnan (#54)
what
This adds the option to turn on MFA Delete for the bucket.
why
issue #48 does a good job explaining, but pasted important information below
Security best practices for CloudTrail logs that are stored in S3 recommend MFA Delete be enabled.
https://www.cloudconformity.com/knowledge-base/aws/CloudTrail/cloudtrail-bucket-mfa-delete-enabled.html
references
closes #48
v0.20.0
Compare Source
context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#53)
what
why
v0.19.0
Compare Source
minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#52)
what
why
v0.18.1
Compare Source
🤖 Automatic Updates
Update README.md and docs @cloudpossebot (#51)
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
v0.18.0
Compare Source
Bc compliance @maximmi (#49)
what
S3 bucket MFA delete
enabled by defaultS3 Bucket Versioning
enabled by defaultEncryption of the S3 bucket
enabled by defaultwhy
references
v0.17.0
Compare Source
Terraform 0.14 upgrade @maximmi (#46)
what
why
v0.16.0
Compare Source
Terraform 0.14 upgrade @Nuru (#44)
what
why
v0.15.1
Compare Source
Configure Renovate @renovate (#40)
Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.
Detected Package Files
.github/workflows/auto-release.yml
(github-actions).github/workflows/chatops.yml
(github-actions)context.tf
(terraform)versions.tf
(terraform)Configuration
🔡 Renovate has detected a custom config for this PR. Feel free to ask for help if you have any doubts and would like it reviewed.
Important: Now that this branch is edited, Renovate can't rebase it from the base branch any more. If you make changes to the base branch that could impact this onboarding PR, please merge them manually.
What to Expect
With your current configuration, Renovate will create 1 Pull Request:
Update cloudposse/actions action to v0.22.0
renovate/cloudposse-actions-0.x
master
0.22.0
❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.
This PR has been generated by WhiteSource Renovate. View repository job log here.
v0.15.0
Compare Source
Support terraform v0.14 @dmattia (#42)
v0.14.0
Compare Source
Update to `context.tf`. Update Terratest to Golang modules. Update GitHub Actions. Allow TF 0.13 @aknysh (#39)
what
context.tf
why
v0.13.1
Compare Source
v0.13.0
Compare Source
v0.12.0
: Allow access logging to be enabledCompare Source
Allow access logging to be enabled on s3 bucket
what
access_log_bucket_name
to be target bucket for access logswhy
expect s3 buckets to have access logs enabled
references
v0.11.0
Compare Source
Adding
enabled
count attribute to bucket policyv0.10.0
Compare Source
Adding abort_incomplete_multipart_upload_days
Match lyfecycle rules from https://github.com/cloudposse/terraform-aws-s3-bucket
v0.9.0
: Add blocking of public access to the bucketCompare Source
what
why
v0.8.0
: Optional transitions to glacierCompare Source
what
why
v0.7.0
: Update to latest label module to support the environment attributeCompare Source
what
why
environment
attribute is useful for naming resources (along withnamespace
,stage
andname
), and the latest version oflabel
module supports itv0.6.0
Compare Source
v0.5.0
: Convert to TF 0.12. Add tests. Add Codefresh test pipelineCompare Source
what
bats
andterratest
for the exampleterraform-modules
projectwhy
terraform-modules
project contains pipelines for all terraform modulesv0.4.1
Compare Source
v0.4.0
: Fix lifecycle tagsCompare Source
what
why
The
tags
generated by the label module were propagated to the S3 Lifecycle filters, this is in general not desired, as it means the lifecycle only applies to objects with those tags.Console help message for the setting:
This adds a new var
lifecycle_tags
which is a map of the tags to apply to the lifecycle rule.references
v0.3.1
: Update readme yaml file and rebuild mdCompare Source
what
README.yaml
fileREADME.md
filewhy
v0.3.0
: Add enabled flagCompare Source
what
why
v0.2.2
: Regenerate README.mdCompare Source
what
README.md
why
v0.2.1
: Migrate to README.yaml formatCompare Source
what
README.yaml
why
v0.2.0
Compare Source
what
why
references
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 has been generated by Mend Renovate. View repository job log here.