v0.28.0

Terraform 0.14 upgrade @maximmi (#67)

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

v0.27.0

Allow current object expiration to be disabled. @davidski (#66)

what

Adds a new option - "enable_current_object_expiration" for selectively disabling current object expiration.
Default to true to maintain behavior with existing versions.

why

Users that wish to enable versioning for deletion protection, multipart upload cleanup, etc. may not wish objects to be
completely deleted (even after other lifecycle changes). Currently, it is not possible to opt into the core data
preservation and cost control features of lifecycle policies without also getting old object expiration.

references

Reference this thread on the SweetOps slack: https://sweetops.slack.com/archives/CB6GHNLG0/p1605633214288700

v0.26.0

make this module v14 compatible @jurgenweber (#65)

make this module v14 compatible

v0.25.0

Fix version clash with other cloudposse repos @richardARPANET (#58)

I was using some of your other aws terraform projects and because they want version ~> 2.0 mostly. And this one wants >3.0 then it would not work:

Error: provider.aws: no suitable version installed
  version requirements: ">= 2.0,>= 2.0,>= 2.0,>= 2.0,>= 3.0,>= 3.0,~> 2.0,~> 2.0,~> 2.0,~> 2.0,~> 2.0,~> 2.0,~> 2.0"
  versions installed: "2.70.0"

So I've relaxed the requirement in this repo to resolve this.

v0.24.0

Adding support for s3 bucket replication configuration @danjbh (#56)

what

• Adding support for custom replication_configuration definition
• Adding master flag to enable/disable s3 bucket replication
• Adding input variable for ARN of destination bucket
• Creates all required IAM roles/policies

NOTE: The destination bucket must already exist!

why

• Allows the user to enable s3 bucket replication and define custom rules, filters, etc!

v0.23.0

Add support for bucket logging @tacchino (#57)

what

• Add support for configuration of bucket access logs

why

• Missing API support

references

• Closes #10

v0.22.0

Update to context. @Iouns (#54)

Update to context

what

• Update to context.
• Terraform aws provider v3 compatibility

why

• N/A

references

• Dependency on cloudposse/terraform-aws-iam-s3-user#22

0.21.0 Use minimum versions for provider pinning

what

• Set minimum versions for providers without pinning to a specific major version

why

• the current method makes it very difficult to maintain or upgrade consistent provider versions within a project

related

• Closes #46

references

https://www.terraform.io/docs/configuration/provider-requirements.html#best-practices-for-provider-versions
cloudposse/terraform-aws-iam-system-user#33
cloudposse/terraform-aws-iam-s3-user#19

0.20.0 Update AWS provider pinning to v3 for TF 0.13 version compat

what

• Do not restrict the aws provider version to just v2

why

cloudposse/terraform-aws-route53-cluster-hostname#23
the aws cloud provider has v13 fixes and requirements also

references

closes #46
#46

0.19.0 Remove hardcoded ARN partition

what

• Remove hardcoded ARN partition

why

• The module hardcodes the partition component of the ARN, making it impossible to use this module in other partitions
• This change will allow to seamlessly support other AWS partitions such as aws-us-gov
• This change is a NOOP for existing resources

references

• See Amazon ARN syntax