This module creates an S3 bucket suitable for receiving logs from other AWS services such as S3, CloudFront, and CloudTrail
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/s3-bucket/aws (source) | module | patch | 3.1.2 -> 3.1.3 |
v3.1.3
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.
var.source_policy_documents
to local.source_policy_documents
so var.policy
usage was still supportedvar,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 executeRebuild '.github' dir from the template
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/s3-bucket/aws (source) | module | patch | 3.1.1 -> 3.1.2 |
v3.1.2
: Fix Public Bucket CreationFull Changelog: https://github.com/cloudposse/terraform-aws-s3-bucket/compare/3.1.1...3.1.2
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/s3-bucket/aws (source) | module | patch | 3.1.1 -> 3.1.2 |
v3.1.2
: Fix Public Bucket CreationFull Changelog: https://github.com/cloudposse/terraform-aws-s3-bucket/compare/3.1.1...3.1.2
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/s3-bucket/aws (source) | module | patch | 3.1.0 -> 3.1.1 |
v3.1.1
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/s3-bucket/aws (source) | module | patch | 3.1.0 -> 3.1.1 |
v3.1.1
lifecycle_configuration_rules
to be fully defined with optional membersThis PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/s3-bucket/aws (source) | module | minor | 3.0.0 -> 3.1.0 |
v3.1.0
aws_s3_bucket_accelerate_configuration
and aws_s3_bucket_versioning
resources even when the feature is disabled, to enable drift detectionaws_s3_bucket_versioning
resource to track changes made to bucket versioning configurationaws_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 the aws_s3_bucket_versioning
resource exists.This is an auto-generated PR that updates the README.md and docs
To have most recent changes of README.md and doc from origin templates
bucket_key_enabled
flag defaults to false
for backward compatibility. At one point we recommend setting it to true for significant savings on KMS usage, but since bucket keys are only reused within a user session, it is not clear if it provides any savings at all. See AWS docs for more information.lifecycle_configuration_rules
input replaces the now deprecated individual inputs for individual settings of a single lifecycle rule. See the terraform-aws-s3-bucket documentation for details on how to specify lifecycles using lifecycle_configuration_rules
. This mechanism is much more flexible and closely follows the Terraform aws_s3_bucket_lifecycle_configuration
resource.source_policy_documents
input replaces the now deprecated policy
input to match changes to the aws_iam_policy_document
resourcenull
force_destroy
at its default value of false
, and if you have it set to true
but want extra safety against the S3 bucket being destroyed, set it to false
before upgrading).force_destroy_enabled
flag introduced in v0.27.0 has been removedlifecycle_configuration_rules
input was introduced. In that version, you would continue to get the old default lifecycle rule even if you supplied new rules via lifecycle_configuration_rules
. Now, the default behavior is to ignore all the deprecated lifecycle inputs when the lifecycle_configuration_rules
input is not empty, unless you explicitly set lifecycle_rule_enabled
to true.moved
block functionality introduced in Terraform 1.3.0nullable = false
for module input variables which have a default value and where null is not a sensible/handled value for the variable.null
, closes #63With 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.
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/s3-bucket/aws (source) | module | major | 2.0.1 -> 3.0.0 |