Releases: cloudposse/terraform-aws-s3-website
v0.15.4
🤖 Automatic Updates
Update context.tf @cloudpossebot (#59)
what
This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label
why
To support all the features of the context interface.
v0.15.3
🤖 Automatic Updates
Update Terraform cloudposse/s3-log-storage/aws to v0.19.0 @renovate (#49)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/s3-log-storage/aws (source) | terraform | minor | 0.16.0 -> 0.19.0 |
Release Notes
cloudposse/terraform-aws-s3-log-storage
v0.19.0
minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#52)
#### what - update context.tf to v0.23.0 - minimum required Terraform version bumped to 0.13.0 - readme updated, Bridgecrew compliance badges added #### why - It allows for setting the letter case of tag names and labels - we have dropped support for Terraform 0.12 - To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliantv0.18.1
🤖 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 templatesv0.18.0
Bc compliance @maximmi (#49)
#### what * BridgeCrew compliance checks fix * readme updated * default behaviour changed: `S3 bucket MFA delete` enabled by default * default behaviour changed: `S3 Bucket Versioning` enabled by default * default behaviour changed: `Encryption of the S3 bucket` enabled by default #### why * To be able to position our modules as standards compliant * stay in sync with code * To comply BridgeCrew check #### references * https://docs.bridgecrew.io/docs/s3_16-enable-versioning * https://docs.bridgecrew.io/docs/s3_13-enable-logging * https://docs.bridgecrew.io/docs/s3_14-data-encrypted-at-restv0.17.0
Terraform 0.14 upgrade @maximmi (#46)
#### what - Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard #### why - Support Terraform 0.14v0.15.2
🤖 Automatic Updates
Update Terraform cloudposse/label/null to v0.24.1 @renovate (#57)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/label/null (source) | terraform | patch | 0.24.0 -> 0.24.1 |
Release Notes
cloudposse/terraform-null-label
v0.24.1
Allow control of letter case of outputs @SweetOps (#107)
You now have control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id.
Labels are the elements you can include in label_order, namely namespace, environment, stage, name, and attributes. For every non-empty label, a corresponding tag name is generated. For namespace, environment, stage, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars.), For attributes, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter (defaults to hyphen). For name, which is special, the output is the same as id, which is the joining of the labels in the order specified by label_order and separated by delimiter.
- You can set
label_key_caseto one ofupper,lower, ortitle, which will result in generatedtagnames in the corresponding case:NAME,name, orName. For backwards compatibility,titleis the default - You can set
label_value_caseto one ofupper,lower,title, ornone, which will result in output label values in the corresponding case (withnonemeaning no case conversion of any kind will be done, though the labels will still be subject toregex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in thetagvalues and in theidstring.
You can look at the test cases in examples/complete and the expected results in test/src/examples_complete_test.go to see examples of how this is supposed to work.
One interesting example is that you can create ids in Pascal case by setting label_value_case = "title" and delimiter = "".
Include updates to exports/context.tf @Nuru (#122 and #123)
#### what - Include updates to `exports/context.tf` - Update README with features and compatibilty - Add validation for `id_length_limit` #### why - The `exports/context.tf` is what gets distributed and needs to be in sync - Replace outdated information - Was not validated earlier because validators are not supported in TF 0.12 but now we are dropping support for TF 0.12 and so we can add validatorsRestore backward compatibility with v0.22.1 and earlier @Nuru (#121)
#### what - Restore backward compatibility with v0.22.1 and earlier - Allow setting of `label_key_case` and `label_value_case` by vars, not just by context attributes. #### why - Allow interoperability of old and new modules - Normally, root modules make settings via individual variables, not by setting an entire context block.Incorporates and closes #120
v0.15.1
🤖 Automatic Updates
Update Terraform cloudposse/label/null to v0.24.0 @renovate (#53)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/label/null (source) | terraform | minor | 0.22.1 -> 0.24.0 |
Release Notes
cloudposse/terraform-null-label
v0.24.0
Restore backward compatibility with v0.22.1 and earlier @Nuru (#121)
##### what - Restore backward compatibility with v0.22.1 and earlier - Allow setting of `label_key_case` and `label_value_case` by vars, not just by context attributes. ##### why - Allow interoperability of old and new modules - Normally, root modules make settings via individual variables, not by setting an entire context block.Incorporates and closes #120
Allow control of letter case of outputs @SweetOps (#107)
You now have control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id.
Labels are the elements you can include in label_order, namely namespace, environment, stage, name, and attributes. For every non-empty label, a corresponding tag name is generated. For namespace, environment, stage, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars.), For attributes, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter (defaults to hyphen). For name, which is special, the output is the same as id, which is the joining of the labels in the order specified by label_order and separated by delimiter.
- You can set
label_key_caseto one ofupper,lower, ortitle, which will result in generatedtagnames in the corresponding case:NAME,name, orName. For backwards compatibility,titleis the default - You can set
label_value_caseto one ofupper,lower,title, ornone, which will result in output label values in the corresponding case (withnonemeaning no case conversion of any kind will be done, though the labels will still be subject toregex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in thetagvalues and in theidstring.
You can look at the test cases in examples/complete and the expected results in test/src/examples_complete_test.go to see examples of how this is supposed to work.
One interesting example is that you can create ids in Pascal case by setting label_value_case = "title" and delimiter = "".
v0.23.0
- feat: add support for setting letter case of context tags @SweetOps (#107)
With this release, you gain control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id.
Labels are the elements you can include in label_order, namely namespace, environment, stage, name, and attributes. For every non-empty label, a corresponding tag name is generated. For namespace, environment, stage, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars.), For attributes, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter (defaults to hyphen). For name, which is special, the output is the same as id, which is the joining of the labels in the order specified by label_order and separated by delimiter.
- You can set
label_key_caseto one ofupper,lower, ortitle, which will result in generatedtagnames in the corresponding case:NAME,name, orName. For backwards compatibility,titleis the default - You can set
label_value_caseto one ofupper,lower,title, ornone, which will result in output label values in the corresponding case (withnonemeaning no case conversion of any kind will be done, though the labels will still be subject toregex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in thetagvalues and in theidstring.
You can look at the test cases in examples/complete and the expected results in test/src/examples_complete_test.go to see examples of how this is supposed to work.
One interesting example is that you can create ids in Pascal case by setting label_value_case = "title" and delimiter = "".
v0.15.0
minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#55)
what
- update context.tf to v0.23.0
- minimum required Terraform version bumped to 0.13.0
- readme updated, Bridgecrew compliance badges added
why
- It allows for setting the letter case of tag names and labels
- we have dropped support for Terraform 0.12
- To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant
v0.14.0
v0.13.0
v0.12.0
0.11.1: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#41)
## What 1. Update Version Pinning for Terraform to support 0.13 ## Why 1. This is a relatively minor update that the CloudPosse module already likely supports. 1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.