Skip to content

v0.3.1
Compare
Choose a tag to compare
@cloudpossebot cloudpossebot released this 21 Apr 00:53
0.3.1
4991191
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

🤖 Automatic Updates

Update Terraform cloudposse/s3-bucket/aws to v2 @renovate (#12)

This PR contains the following updates:

Package Type Update Change
cloudposse/s3-bucket/aws (source) module major 0.49.0 -> 2.0.0

Release Notes

cloudposse/terraform-aws-s3-bucket

v2.0.0

Compare Source

Version 2.0 of terraform-aws-s3-bucket is the same as v0.49.0 except for the addition of 2 small bug fixes (see #​147). It is labeled v2.0 as part of Cloud Posse's transition to production Semantic Versioning conventions, and to indicate significant changes as compared to v1.0 (essentially version 0.47.1). There are some quirks to be aware of:

  • NO ACTION IS NEEDED to upgrade directly from v0.49.0 to v2.0.0
  • Version 1.0 derives from and is compatible with version 0.47.1. Follow the upgrade instructions if upgrading from one of these versions.
  • Version 0.48.0 was an interim release that is not recommended for anyone to use. It has incompatibilities with every other version. If you are on v0.48.0, you can upgrade directly to v2.0.0 and if Terraform gives you no complaints, then you are good to go. See the release notes for v0.48.0 and v0.49.0 for information about how to fix any breakage.
Bug fixes @​Nuru (#​147) ##### what && why - Require AWS provider v4.9.0 or later, resolves #​137 - Properly consider `source_policy_documents` input, fixes #​145

v1.0.0

Compare Source

Version 1.0.0 is part of Cloud Posse's conversion to production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature modules, especially those where we see breaking changes coming in the near future. In the case of this module, the breaking changes have already been released as v2.0.0. This is a quirk due to not previously using production Semantic Versioning.

TAKE NOTE:

  • Despite the 1.0 version designation, it is actually not compatible with the latest previous release (v0.49.0) or the current recommended release (v2.0.0). Because of that, this version is only recommended for people currently using v0.47.1 or earlier.
  • This release is the same as v0.47.1 except for additional version pinning allowing it to work with AWS provider v4.
  • No maintenance is planned for v1. With the release of AWS provider v4.9.0, the upgrade to v2.0 of this module requires no manual intervention as long as you meet the prerequisites (AWS provider v4.9.0 or later, Terraform v1.0.0 or later). So we recommend upgrading to v2.0 to get any bug fixes or new features.

Contributors

renovate
Assets 2
Loading