v0.50.2

🚀 Enhancements

Add optional `subnet_group_name` input to override the name @tjarjoura (#133)

what

• Allow the user to specify the db_subnet_group name, rather than using the default label ID

why

• If importing an existing database cluster and subnet group, we need to be able to set the subnet group name to what it already has, otherwise the subnet group will be recreated. This in turn will cause the database cluster to be recreated, which we don't want.

references

• https://sweetops.slack.com/archives/CB6GHNLG0/p1646336110444589

v0.50.1

🚀 Enhancements

Add enhanced monitoring attributes @nitrocode (#131)

what

• Add enhanced monitoring attributes

why

• The name can be too long at times and exposing this input could prevent the following error

│ Error: expected length of name to be in the range (1 - 64), got snip-snip-snip-snip-aurora-global-example-shared-enhanced-monitoring
│
│   with module.primary_aurora_postgres_cluster.aws_iam_role.enhanced_monitoring[0],
│   on .terraform-mdev/modules/primary_aurora_postgres_cluster/enhanced-monitoring.tf line 17, in resource "aws_iam_role" "enhanced_monitoring":
│   17:   name               = module.enhanced_monitoring_label.id

references

• Test results https://github.com/cloudposse/actions/actions/runs/1895037399
• Closed #132

v0.50.0

Add support for disabling egress traffic @jalgraves (#130)

what

• Add support for disabling egress security-group rule in default security group

why

tl;dr My boss told me to.

We had a third party do a pen test and afterwards they suggested we remove egress traffic from our DB subnets. If I'm missing something and there is another way to accomplish this without changing the module I'd be happy and grateful to hear it.

v0.49.2

🚀 Enhancements

Create dns record if not serverless @nitrocode (#128)

what

• Restore original logic

why

• Previous logic was to create the record when module was not serverless

references

• Previous PR #124

v0.49.1

🚀 Enhancements

Flag `master_username` output as sensitive @batistadasilva (#114)

what

• Flag master_username output as sensitive

why

Running on Terraform Cloud

Terraform v0.14.5
Configuring remote state backend...
Initializing Terraform configuration...

Error: Output refers to sensitive values

  on .terraform/modules/db/outputs.tf line 6:
   6: output "master_username" {

Expressions used in outputs can only refer to sensitive values if the
sensitive attribute is true.

references

• https://www.terraform.io/upgrade-guides/0-14.html#sensitive-values-in-plan-output

v0.49.0

fix: prevent creating empty replicas record @syphernl (#126)

what

• Prevent creating empty DNS replicas record when cluster_size < 1

why

• If the cluster_size = 0 this would result in an attempt to create an empty DNS record, which is not permitted by the Route53 API

references

• Follow-up to changes done in #124

v0.48.1

🚀 Enhancements

Update AWS provider minimum version @alexjurkiewicz (#125)

what

• c96d859 added performance_insights_retention_period, which is supported in AWS provider v3.63.0 onwards.

why

• Prevent issues with older cached aws providers

references

N/A

v0.48.0

Additional inputs @nitrocode (#124)

what

• Add performance_insights_retention_period
• Add ca_cert_identifier
• Add preferred_maintenance_window to instances
• Add timeout to instances

why

• Performance insights retention
• Add a ca cert identifier
• Put the maintenance window on cluster and instances
• Allow rds instances to be created without hitting a timeout

v0.47.2

🤖 Automatic Updates

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

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, check this box.

---

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

v0.47.1

🤖 Automatic Updates

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

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/route53-cluster-hostname/aws (source)	module	patch	0.12.0 -> 0.12.2

---

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

v0.12.2

Compare Source

🚀 Enhancements

Bump AWS provider 3.0 @​nitrocode (#​36)

##### what * Bump AWS provider 3.0 ##### why * Downstream modules can take advantage of the more recent aws provider ##### references N/A

v0.12.1

Compare Source

🚀 Enhancements

Chore: run `make github/init` @​korenyoni (#​37)

##### what * Run `make github/init`. ##### why * Updates GHA-workflow-related files to their latest distribution. * The old `context.tf` distribution is incompatible with the `tenant` label. ##### references * https://github.com/cloudposse/terraform-null-label/releases/tag/0.25.0

---

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, check this box.

---

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