Skip to content

Releases: cloudposse/terraform-aws-rds

v0.32.3

04 Feb 20:44
078937c

Choose a tag to compare

🤖 Automatic Updates

chore(deps): update terraform cloudposse/route53-cluster-hostname/aws to v0.12.0 @renovate (#104)

This PR contains the following updates:

Package Type Update Change
cloudposse/route53-cluster-hostname/aws (source) terraform minor 0.11.0 -> 0.12.0

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

v0.12.0

Compare Source

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @​maximmi (#​35) #### what - update context.tf to v0.24.1 - 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, back compatibility with context v0.22.0 and below - 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.32.2

04 Feb 10:24
52208ff

Choose a tag to compare

🤖 Automatic Updates

chore(deps): update terraform cloudposse/label/null to v0.24.1 @renovate (#101)

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

Compare Source

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_case to one of upper, lower, or title, which will result in generated tag names in the corresponding case: NAME, name, or Name. For backwards compatibility, title is the default
  • You can set label_value_case to one of upper, lower, title, or none, which will result in output label values in the corresponding case (with none meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag values and in the id string.

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 validators
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

v0.32.1

04 Feb 09:06
6c50d09

Choose a tag to compare

v0.32.1 Pre-release
Pre-release

🤖 Automatic Updates

chore(deps): update terraform cloudposse/label/null to v0.24.0 @renovate (#100)

This PR contains the following updates:

Package Type Update Change
cloudposse/label/null (source) terraform minor 0.23.0 -> 0.24.0

Release Notes

cloudposse/terraform-null-label

v0.24.0

Compare Source

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_case to one of upper, lower, or title, which will result in generated tag names in the corresponding case: NAME, name, or Name. For backwards compatibility, title is the default
  • You can set label_value_case to one of upper, lower, title, or none, which will result in output label values in the corresponding case (with none meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag values and in the id string.

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.32.0

04 Feb 04:53
5ac9a66

Choose a tag to compare

minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#99)

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

Supersedes and closes #96
Supersedes and closes #97
Supersedes and closes #98

v0.31.0

26 Jan 04:49
5e99e93

Choose a tag to compare

storage_encrypted default value changed to true @maximmi (#92)

what

  • BridgeCrew compliance checks fix
  • readme updated
  • default behaviour changed: RDS Instance Encryption enabled by default

why

  • To be able to position our modules as standards compliant
  • stay in sync with code
  • To comply BridgeCrew check

references

v0.30.0

07 Jan 18:00
ab39f6a

Choose a tag to compare

Added Microsoft SQL Server example @amitkarpe (#79)

what

  • Added Microsoft SQL Server example

why

  • There was MySQL RDS example but nothing for MSSQL

v0.29.0

06 Jan 17:22
b1e02e4

Choose a tag to compare

Terraform 0.14 upgrade @maximmi (#89)

what

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

why

  • Support Terraform 0.14

v0.28.2

06 Jan 16:57
f947533

Choose a tag to compare

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#88)

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 templates

v0.28.1

28 Dec 08:04
c682edb

Choose a tag to compare

🤖 Automatic Updates

chore(deps): update terraform cloudposse/label/null to v0.22.1 @renovate (#84)

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
cloudposse/label/null (source) terraform patch 0.22.0 -> 0.22.1

Release Notes

cloudposse/terraform-null-label

v0.22.1

Compare Source

Add var.attributes to end of context.attributes, not vice versa @​Nuru (#​114) #### what - Add `var.attributes` to end of `context.attributes`, not vice versa - Update to current workflows (with some exceptions) #### why - Modules should append to attributes passed in, not insert themselves ahead of others - New features, like auto-format (but holding back some, because this is a special module) #### references - closes #​113 - closes #​108

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

v0.28.0

28 Dec 07:17
ba59189

Choose a tag to compare

Clarify description of db_parameter_group @yariksheptykin (#67)

Documentation of the db_parameter_group variable is somewhat obscure with regard to possible values it intakes. It actually expects a name of DB parameter group family, which can be one of many pre-defined families provided by AWS. The list of supported families is quite hidden in AWS Documentation so I suggest placing a link to the right place stright into the variable description.