v0.18.0

Add master_password output to return generated password. @petur (#45)

what

• Add a master_password output for the generated password.

why

• The generated password needs to be stored somewhere so that it's possible to use it to connect to the cluster.
• This can for example be done by storing it in an aws_secretsmanager_secret_version as part of the terraform configuration that creates the cluster.
• Exposing the password as a module output makes it available to other parts of the configuration so that the password can be passed to the resource that stores it.

references

• closes #43

Sync github @max-lobur (#60)

Rebuild github dir from the template

v0.17.1

Sync .github @max-lobur (#58)

Sync github workflows with the template

🚀 Enhancements

fix: propagate `preferred_maintenance_window` to the docdb cluster instances resources @sherifkayad (#57)

propagated preferred_maintenance_window to the docdb cluster instances resources

what

• The maintenance window given as a variable is given to the Terraform Resource aws_docdb_cluster_instance.default such that the cluster and its instances have the same value given by the user
• Closes #55

why

• Without that the cluster instances were having "random" windows that don't match the expectations of "potential" down time
• Users want to be in control of when their databases can go under maintenance not just at any "random" time

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/docdb_cluster_instance#preferred_maintenance_window

v0.17.0

• No changes

v0.16.0

feat: add enable performance insights @brunordias (#50)

what

• Add optional enable Performance Insights for the DB Instance.

why

• Is very helpful the option to enable Performance Insights for the DB Instance.

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/docdb_cluster_instance#enable_performance_insights

git.io->cloudposse.tools update @dylanbannon (#46)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143

v0.15.0

Generate random password when master_password is empty @dkossako (#42)

what

• If master_password is not provided or empty random value will be used

why

• AWS API requires to provide password
• Secrets should not be kept in repository

v0.14.1

🤖 Automatic Updates

Update Terraform cloudposse/route53-cluster-hostname/aws to v0.12.2 @renovate (#38)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/route53-cluster-hostname/aws (source)	module	patch	0.12.1 -> 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

---

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

Fix: Make `engine_version` explicit by default, run `make github/init`, update module versions. @korenyoni (#37)

what

• Make engine_version explicit by default.
• Run make github/init.
• Update module versions.

why

• engine_version defaults to the latest docdb version — 4.0.0 — which is incompatible with the docdb3.6 cluster family.
• Updates GHA-workflow-related files to their latest distribution.
• The old context.tf distribution is incompatible with the tenant label.
• The old module versions have a context.tf distribution that is incompatible with the tenant label.

references

• https://github.com/cloudposse/terraform-null-label/releases/tag/0.25.0

v0.13.0

Add deletion_protection parameter @krsh-off (#32)

what

Add deletion_protection parameter to the module as an additional safeguard for production systems. This PR addresses issue #30.

why

The absence of this feature is required us to implement local-exec or any other custom logic. This pretty small change provides an ability to use the module as-is.

v0.12.1

🤖 Automatic Updates

Update Terraform cloudposse/route53-cluster-hostname/aws to v0.12.0 @renovate (#29)

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

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

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