v0.38.2

🤖 Automatic Updates

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

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/label/null (source)	module	minor	0.24.1 -> 0.25.0

---

Release Notes

cloudposse/terraform-null-label

v0.25.0

Compare Source

Add "tenant", "labels_as_tags", and "descriptors" @​Nuru (#​132)

##### what - Add additional label and `id` component: `tenant` - New input `labels_as_tags` controls which labels are exported as tags - New input `descriptor_formats` generates new output `descriptors` - Update README, remove link to obsolete `terraform-terraform-label` ##### why - Support users that host resources on behalf of and/or dedicated to single customers - Supersedes and closes #​131, giving people control over which tags the module generates - Simple mechanism for creating multiple identifiers from the same inputs, reducing the need to create multiple instances of `null-label` - Document `tenant`, `labels_as_tags`, `descriptor_formats`, add additional clarification, stop promoting obsolete module

Fix: Update README Snippets @​korenyoni (#​130)

##### what * Update README snippets to reflect use of Terraform Registry. ##### why * Including snippets that reflect use of the Terraform Registry make it easier for users to quickly instantiate a null_label module. * README is out of date and does not include snippets that reflect use of the Terraform Registry. ##### references * N/A

Bridgecrew compliance @​Nuru (#​125)

##### what - Resolve Bridgecrew compliance complaint about example Autoscaling Group (BC_AWS_GENERAL_31) - Fix typo in README - Include Terraform lock file in `.gitignore` ##### why - Get clean Bridgecrew badge - Correct confusing error - Ensure lock files are not checked into GitHub ##### note The PR can and should be merged into `master` to update README and Bridgecrew without triggering a new release/version. These changes have no effect on the actual module in use and a release will create unnecessary ripple effects. However, merging to `master` will update the README and badges, so is worthwhile, and the changes will move forward into the next release.

Properly output descriptors of chained modules @​Nuru (#​133)

##### what - Properly output descriptors of chained modules ##### why - Bug fix; implement intended behavior

---

Configuration

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

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

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

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

---

• If you want to rebase/retry this PR, click this checkbox.

---

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

v0.38.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#122)

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

Add `replicate_source_db` @nitrocode (#120)

what

• Add replicate_source_db

why

• Create a read replica

references

• Closes #113
• May remove the need to maintain https://github.com/cloudposse/terraform-aws-rds-replica

v0.37.0

Add option to define character set @yariksheptykin (#71)

Closes #70

v0.36.0

Setting ca_cert_identifier default value to null @nnsense (#115)

what

Setting ca_cert_identifier default value to null, leaving its resolution up to the AWS resource.

why

Creating RDS in newer regions such as eu-south-1, ap-east-1, me-south-1, af-south-1 errors but RDS instance is still created. The default CA certificate ID (rds-ca-2019), which is valid across most of the regions, has a different format on these, see: #114 (comment)

references

• #114
• closes #114

v0.35.1

🚀 Enhancements

Add an output to export resource_id @jblackburn22 (#112)

what

• Exports the resource_id

why

• The resource_id is needed in order to create a least-privileges IAM policy to provide using RDS IAM authentication.

references

• Use closes #111

v0.35.0

Add `create_before_destroy` for parameter group. Make subnet group optional @aknysh (#110)

what

• Add create_before_destroy for parameter group
• Make the names for parameter & option groups unique
• Make subnet group optional
• Bump module versions
• Update example and terratest

why

• You cannot delete a parameter/option group while it is in use, but you can update a database with a new parameter/option group, so in order to change parameter/option groups, you need to create a new one, install it, then delete the old one
• Some update and destroy operations were failing because resources were being deleted in the wrong order
• If var.db_subnet_group_name is provided, use it and don't create a new Subnet Group
• If var.availability_zone is provided (and var.db_subnet_group_name and var.subnet_ids are not), use var.availability_zone to place the instance into the default VPC or EC2 Classic

related

• Closes #93
• Closes #107
• Closes #108
• Closes #109

v0.34.0

Terraform 0.13 requires snapshot_identifier explicitly set to null @nnsense (#106)

what

• With terraform 0.13 If snapshot_identifier is set to "" then the resource creation will fail ("snapshot_identifier": conflicts with username).
• Apparently it works with >0.14 instead.

why

It seems resource "aws_db_instance" "default" defined into main changed (apparently, an hour ago?) its flexibility in taking arguments. Before (also with 0.13) defining "" was enough to use username and password for the DB. Now, I've got this:

Error: ConflictsWith                                                                                                                                                                       
                                                                                             
  on .terraform/modules/rds_instance/main.tf line 44, in resource "aws_db_instance" "default":                                                                                             
  44:   snapshot_identifier         = var.snapshot_identifier                                                                                                                              
                                                                                                                                                                                           
"snapshot_identifier": conflicts with username 

references

No references, and I might even be wrong, I rely on your testing to confirm the issue ;)

v0.33.0

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#103)

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

🤖 Automatic Updates

Update context.tf @cloudpossebot (#105)

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.