Skip to content

v2.0.0 AWS provider v4/v5 compatibility
Compare
Choose a tag to compare
@cloudpossebot cloudpossebot released this 20 Apr 23:50
2.0.0
72ec560
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.

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). Additional upgrade information is in the repo Wiki

Breaking change:

  • The website_inputs are broken (see #141). When we get them fixed, we will likely deprecate the variable in favor of new variables that include new features available in the provider. If you are using website_inputs, do not upgrade to v2.x until #141 is closed.

Additional notes

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

Contributors

Nuru
Assets 2
Loading