Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.30.0 #7

renovate-bot · 2023-10-23T02:32:26Z

This PR contains the following updates:

Package	Type	Update	Change
github.com/cloudposse/terraform-aws-documentdb-cluster	module	minor	`tags/0.13.0` -> `v0.30.0`
github.com/cloudposse/terraform-aws-documentdb-cluster	module	minor	`tags/0.8.0` -> `v0.30.0`

Release Notes

cloudposse/terraform-aws-documentdb-cluster (github.com/cloudposse/terraform-aws-documentdb-cluster)

`v0.30.0`

Compare Source

No changes

`v0.29.0`

Compare Source

Revert "chore: Replace Makefile with atmos.yaml" @goruha (#120)

Reverts cloudposse/terraform-aws-documentdb-cluster#119

`v0.28.0`

Compare Source

chore: Replace Makefile with atmos.yaml @osterman (#119)

what

deprecate build-harness

`v0.27.0`

Compare Source

fix: address invalid count bug @RoseSecurity (#118)

what and why

If a data.aws_ssm_parameter.password.value is passed to this module, it is tagged as a sensitive in the AWS provider, and that tag travels with the value all the way into the module. Because we don’t mark variable master_password as sensitive = true, the value is off-limits to functions like length() or to meta-arguments like count. Terraform refuses to evaluate them → “invalid count argument”.

`v0.27.0`

Compare Source

fix: address invalid count bug @RoseSecurity (#118)

what and why

If a data.aws_ssm_parameter.password.value is passed to this module, it is tagged as a sensitive in the AWS provider, and that tag travels with the value all the way into the module. Because we don’t mark variable master_password as sensitive = true, the value is off-limits to functions like length() or to meta-arguments like count. Terraform refuses to evaluate them → “invalid count argument”.

`v0.26.3`

Compare Source

🚀 Enhancements

feat: consolidate enable parameters to locals and fix invalid count bug @RoseSecurity (#117)

what

Move enabled logic into locals
Added a local: local.enabled && length(var.master_password) == 0

[!NOTE]
length() returns an integer, so the result is always plan-time-known, even when the underlying string is deferred

Replaced the old count expression with count = module.this.enabled && local.is_master_password_empty ? 1 : 0.

why

Root cause: the count = module.this.enabled && var.master_password == "" ? 1 : 0 expression referenced var.master_password, which, when wired to something like aws_ssm_parameter.db_password.value, is unknown until apply time

references

Resolves:
- https://github.com/cloudposse/terraform-aws-documentdb-cluster/issues/68
- https://github.com/cloudposse/terraform-aws-documentdb-cluster/issues/71

🐛 Bug Fixes

feat: consolidate enable parameters to locals and fix invalid count bug @RoseSecurity (#117)

what

Move enabled logic into locals
Added a local: local.enabled && length(var.master_password) == 0

[!NOTE]
length() returns an integer, so the result is always plan-time-known, even when the underlying string is deferred

Replaced the old count expression with count = module.this.enabled && local.is_master_password_empty ? 1 : 0.

why

Root cause: the count = module.this.enabled && var.master_password == "" ? 1 : 0 expression referenced var.master_password, which, when wired to something like aws_ssm_parameter.db_password.value, is unknown until apply time

references

Resolves:
- https://github.com/cloudposse/terraform-aws-documentdb-cluster/issues/68
- https://github.com/cloudposse/terraform-aws-documentdb-cluster/issues/71

🤖 Automatic Updates

Migrate new test account @osterman (#110)

what

Update .github/settings.yml
Update .github/chatops.yml files

why

Re-apply .github/settings.yml from org level to get terratest environment
Migrate to new test account

References

DEV-388 Automate clean up of test account in new organization
DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
DEV-386 Update terratest to use new testing account with GitHub OIDC

`v0.26.2`

Compare Source

feat: added output cluster_members for resource aws_docdb_cluster @Faris96Hub (#107)

what

Added the Output "cluster_members" for the resource "aws_docdb_cluster".

why

Needed for monitoring reasons of the DocumentDB Cluster on a Node-level. Needed when creating a CloudWatch alarm on Node-level because the Dimesion of the alarm needs the cluster memebers.

references

https://docs.aws.amazon.com/documentdb/latest/developerguide/cloud_watch.html#:~:text=and%20ReadIOPS.-,Amazon%20DocumentDB%20dimensions,-The%20metrics%20for

🤖 Automatic Updates

Update .github/settings.yml @osterman (#109)

what

Update .github/settings.yml
Drop .github/auto-release.yml files

why

Re-apply .github/settings.yml from org level
Use organization level auto-release settings

references

DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @osterman (#108)

what

Update .github/settings.yml
Drop .github/auto-release.yml files

why

Re-apply .github/settings.yml from org level
Use organization level auto-release settings

references

DEV-1242 Add protected tags with Repository Rulesets on GitHub

`v0.26.1`

Compare Source

fix: upgrade aws provider to 5.29.0 to support storage_type @gmeligio (#103)

what

Upgrade terraform-aws-provider to 5.29.0
Add variable for storage_type in the test.

why

storage_type was released in 5.29.0 but the current minimum version is 5.21.0. This change corrects the minimum required version to 5.29.0

references

closes https://github.com/cloudposse/terraform-aws-documentdb-cluster/issues/86

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.29.0

🚀 Enhancements

chore(deps): bump github.com/hashicorp/go-getter from 1.7.4 to 1.7.5 in /test/src @dependabot (#102)

Bumps [github.com/hashicorp/go-getter](https://redirect.github.com/hashicorp/go-getter) from 1.7.4 to 1.7.5.

Release notes

Sourced from github.com/hashicorp/go-getter's releases.

v1.7.5

What's Changed

Prevent Git Config Alteration on Git Update by @dduzgun-security in hashicorp/go-getter#497

New Contributors

@dduzgun-security made their first contribution in hashicorp/go-getter#497

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.4...v1.7.5

Commits

5a63fd9 Merge pull request #497 from hashicorp/fix-git-update
5b7ec5f fetch tags on update and fix tests
9906874 recreate git config during update to prevent config alteration
See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.

🤖 Automatic Updates

chore(deps): bump github.com/hashicorp/go-getter from 1.7.4 to 1.7.5 in /test/src @dependabot (#102)

Bumps [github.com/hashicorp/go-getter](https://redirect.github.com/hashicorp/go-getter) from 1.7.4 to 1.7.5.

Release notes

Sourced from github.com/hashicorp/go-getter's releases.

v1.7.5

What's Changed

Prevent Git Config Alteration on Git Update by @dduzgun-security in hashicorp/go-getter#497

New Contributors

@dduzgun-security made their first contribution in hashicorp/go-getter#497

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.4...v1.7.5

Commits

5a63fd9 Merge pull request #497 from hashicorp/fix-git-update
5b7ec5f fetch tags on update and fix tests
9906874 recreate git config during update to prevent config alteration
See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.

Update .github/settings.yml @osterman (#101)

what

Update .github/settings.yml
Drop .github/auto-release.yml files

why

Re-apply .github/settings.yml from org level
Use organization level auto-release settings

references

DEV-1242 Add protected tags with Repository Rulesets on GitHub

`v0.26.0`

Compare Source

test: update test framework to use latest best practices and reduce boilerplate @gmeligio (#100)

what

Update this module's test framework. Reduce boilerplate and make reusable functions.

Changelog:

Upgrade go to 1.21.
Update test/Makefile and test/src/Makefile from https://github.com/cloudposse/terraform-aws-eks-node-group/tree/e9f908c026d8ca5dc30190a050de68a510ff3983/test
Create framework_test.go and default_test.go, following how it's done in https://github.com/cloudposse/terraform-aws-eks-node-group/blob/e9f908c026d8ca5dc30190a050de68a510ff3983/test/src/framework_test.go
Remove enabled=true from fixtures and add new test TestExamplesCompleteDisabled for when enabled=false
Add Test_ExistingDeployment for faster test cycle, and modify Makefile accordingly
Update dependencies
Migrate test DB Engine from 3.6.0 to 5.0.0

why

Enable testing with OpenTofu
Support automated maintenance

references

[CHORE] Update variable description @RuiSMagalhaes (#99)

what

Updates enabled_cloudwatch_logs_exports variable description
Updates examples
Updates README.md and docs/terraform.md

why

Ir order to have the right list of logs available in the variable description

references

closes #36

🚀 Enhancements

feat(aws_docdb_cluster): add allow_major_version_upgrade argument @gmeligio (#94)

what

This PR adds the argument allow_major_version_upgrade that was released in https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.21.0

It includes with the changes in the test framework from https://github.com/cloudposse/terraform-aws-documentdb-cluster/pull/100 .

why

When upgrading the engine_version to a new major version, allow_major_version_upgrade needs to be enabled for AWS to apply the upgrade.

references

🤖 Automatic Updates

Update release workflow to allow pull-requests: write @osterman (#97)

what

Update workflow (.github/workflows/release.yaml) to have permission to comment on PR

why

So we can support commenting on PRs with a link to the release

Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#96)

what

Update workflows (.github/workflows) to use shared workflows from .github repo

why

Reduce nested levels of reusable workflows

Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#93)

what

Update workflows (.github/workflows) to add issue: write permission needed by ReviewDog tflint action

why

The ReviewDog action will comment with line-level suggestions based on linting failures

Update GitHub workflows @osterman (#92)

what

Update workflows (.github/workflows/settings.yaml)

why

Support new readme generation workflow.
Generate banners

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#91)

what

Install latest GitHub Action Workflows

why

Use shared workflows from cldouposse/.github repository
Simplify management of workflows from centralized hub of configuration

Add GitHub Settings @osterman (#90)

what

Install a repository config (.github/settings.yaml)

why

Programmatically manage GitHub repo settings

Update Scaffolding @osterman (#87)

what

Reran make readme to rebuild README.md from README.yaml
Migrate to square badges
Add scaffolding for repo settings and Mergify

why

Upstream template changed in the .github repo
Work better with repository rulesets
Modernize look & feel

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

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.25.0`

Compare Source

feat: add storage_type parameter @adubeniuk (#79)

what

Amazon has announced IO-optimized storage type for DocumentDB. Support for it has been added since HashiCorp AWS provider version 5.29.0

why

Keep standard as default but also add ability to create IO-optimized DocumentDB clusters.

references

https://aws.amazon.com/about-aws/whats-new/2023/11/amazon-documentdb-i-o-optimized/
https://registry.terraform.io/providers/hashicorp/aws/5.29.0/docs/resources/docdb_cluster#storage_type

feat: allow to attach external SG to the documentDB @rasta-rocket (#69)

what

Hey folks 👋

First of all thanks for the work 💪

Here the goal is to allow the user of the module to attach security groups which are managed outside of the module

why

This is pretty useful, when you have some design where security groups are centrally managed and so outside of the scope of the module

references

Note: If you have any questions don't hesitate to ping me 😉

Cheers ☀️

`v0.24.0`

Compare Source

feat(aws-docdb-cluster): enable the ssm parameter store to record the… @haidargit (#77)

what

In this PR, we can use the Cloud Posse ssm parameter store module to store the documentdb master_password information.

why

The objective behind this PR is to ensure the secure distribution of the docdb cluster's master password within the AWS infrastructure. We can centrally manage and protect sensitive information, increasing operational efficiency.

references

No issue relates to the current improvement.

I have run these required commands.
make init
make readme

Kindly review this PR for documentdb module improvements. Thank you, Cloud Posse Team!

`v0.23.0`

Compare Source

add variable certificate change @rabihaggle (#72)

what

We need to have the possibility to select the certificate we need to use, or directly the default amazon one.

Fix: Don't create random_password resource if not enabled. @petur (#44)

what

Reverse the sense of the enabled variable when deciding the count for the random_password resource.

why

The sense of the variable was backwards - setting enabled to false meant that the count was always set to 1. A minimal configuration to reproduce this is:

module "disabled_docdb" {
source = "../../work/terraform-aws-documentdb-cluster"
enabled = false
vpc_id = ""
subnet_ids = []
}

`v0.21.0`

Compare Source

adding a feature to customize the egress rule @haidargit (#54)

what

Added 4 new variables egress_source_port, egress_dest_port, egress_protocol, and allowed_egress_cidr_blocks for the "aws_security_group_rule" "egress" resource.
By default, the egress rule 0.0.0.0/0 will be created. If user is expected to restrict outbound traffic, they can specify the required values.

why

We propose this PR because there are scenarios where users may want to restrict outbound traffic from their DocDB instances.
if the DocDB cluster is only used internally and do not need to communicate with wide systems or network, users may want to customize the egress rule for 0.0.0.0/0. By providing the option to customize the egress rule, we are giving users a control over their security posture (compliance). For example, our docdb may only connected with internal applications inside the aws eks cluster, or users may integrate their cloud resources with a third party, such as Prisma Cloud or maybe use tfsec as their security scanner, which prompts users to kindly avoid 0.0.0.0/0 for security best practices.

references

This PR will help to cover the minimum egress exposure of the security group, including: #34

Thank you

`v0.20.0`

Compare Source

Support AWS Provider V5 @max-lobur (#63)

what

Support AWS Provider V5
Linter fixes

why

Maintenance

references

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

`v0.19.0`

Compare Source

Enable intra-security group traffic on DB port @kevcube (#61)

what

adds variable allow_ingress_from_self which configures the security group to allow traffic within itself on DB port

why

This is useful in architectures where the db security group will be used to control db access - i.e. it will also be applied to applications.

references

https://github.com/cloudposse/terraform-aws-rds-cluster/pull/145

`v0.18.0`

Compare Source

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`

Compare Source

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`

Compare Source

No changes

`v0.16.0`

Compare Source

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`

Compare Source

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`

Compare Source

🤖 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`

Compare Source

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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 these updates again.

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

This PR was generated by Mend Renovate. View the repository job log.

Summary by CodeRabbit

Chores
- Updated the underlying infrastructure modules to use a newer version for improved stability and compatibility. No changes to user-facing functionality.

…er to v0.30.0

coderabbitai · 2025-05-31T11:46:44Z

Walkthrough

The Terraform configurations for DocumentDB modules in two directories were updated to reference a newer version (v0.30.0) of their external module source. No other changes were made to input variables, resource definitions, or public interfaces.

Changes

File(s)	Change Summary
cool/docdb.tf, sandbox/docdb.tf	Updated DocumentDB module source version to `v0.30.0`

Poem

A hop and a skip, we update with glee,
Our DocumentDBs now versioned to v0.30.0, you see!
No variables changed, no outputs anew,
Just fresher carrots for our Terraform stew.
With paws on the code and whiskers held high,
We leap to new versions—oh my, oh my!
🥕

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 71858a2 and 271afe4.

📒 Files selected for processing (2)

cool/docdb.tf (2 hunks)
sandbox/docdb.tf (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

GitHub Check: gitStream.cm

🔇 Additional comments (3)

sandbox/docdb.tf (1)

35-35:
❓ Verification inconclusive

Verify module version update compatibility.

Ensure bumping the source to ref v0.30.0 does not introduce breaking changes:

No new required inputs or removed parameters (e.g., stage, namespace, cluster_family).

Existing arguments still align with the upstream changelog.

Run the following to validate the upgrade:

🏁 Script executed:
#!/usr/bin/env bash
set -e
cd sandbox
terraform init -backend=false
terraform validate
terraform plan -no-color
rg 'terraform-aws-documentdb-cluster\.git\?ref=(?!v0\.30\.0)'
Length of output: 153
Verify DocumentDB module version bump compatibility

Ensure updating the source reference to v0.30.0 does not introduce breaking changes:

Review the upstream changelog for v0.30.0 to confirm no new required inputs have been added or existing parameters removed.

Confirm that all module invocations still supply every required argument (stage, namespace, cluster_family, etc.).

You can validate references and surface any lingering old versions with:
# List all module source refs in sandbox
rg 'terraform-aws-documentdb-cluster\.git\?ref=' -n sandbox
To compare variable definitions between versions:
# Fetch and diff variables.tf for v0.29.0 vs. v0.30.0
curl -s https://raw.githubusercontent.com/cloudposse/terraform-aws-documentdb-cluster/v0.29.0/variables.tf -o /tmp/vars_0.29.0.tf
curl -s https://raw.githubusercontent.com/cloudposse/terraform-aws-documentdb-cluster/v0.30.0/variables.tf -o /tmp/vars_0.30.0.tf
diff -u /tmp/vars_0.29.0.tf /tmp/vars_0.30.0.tf
If you spot any newly required inputs or removed parameters, update your invocation or pin to a compatible version.
cool/docdb.tf (2)

37-37: Validate compatibility for the first DocumentDB module.

The documentdb module source was updated to v0.30.0. Verify:

No renames or deprecations of inputs in use (stage, namespace, vpc_id, etc.).

The upstream changelog has no breaking changes for this upgrade.

Run terraform init && terraform plan in the cool directory to confirm.

53-53: Apply compatibility checks to the second DocumentDB module.

The second docdb module was also bumped to v0.30.0. Ensure:

Parameters like cluster_family, tags, and security groups remain valid.

Inputs are consistent with the upstream module’s requirements.

Execute a plan to catch any discrepancies.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

renovate-bot requested a review from sulaiman-coder as a code owner October 23, 2023 02:32

renovate-bot changed the title ~~Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.22.0~~ Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.23.0 Oct 24, 2023

renovate-bot force-pushed the renovate/github.com-cloudposse-terraform-aws-documentdb-cluster-0.x branch from ca815da to 7597e5c Compare October 24, 2023 23:42

renovate-bot changed the title ~~Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.23.0~~ Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.24.0 Nov 25, 2023

renovate-bot force-pushed the renovate/github.com-cloudposse-terraform-aws-documentdb-cluster-0.x branch from 7597e5c to 181319b Compare November 25, 2023 11:13

renovate-bot force-pushed the renovate/github.com-cloudposse-terraform-aws-documentdb-cluster-0.x branch from 181319b to a721398 Compare January 30, 2024 23:47

renovate-bot changed the title ~~Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.24.0~~ Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.25.0 Jan 30, 2024

renovate-bot force-pushed the renovate/github.com-cloudposse-terraform-aws-documentdb-cluster-0.x branch from a721398 to 3dc3830 Compare June 30, 2024 05:39

renovate-bot changed the title ~~Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.25.0~~ Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.27.0 Jun 30, 2024

Update Terraform github.com/cloudposse/terraform-aws-documentdb-clust…

271afe4

…er to v0.30.0

renovate-bot force-pushed the renovate/github.com-cloudposse-terraform-aws-documentdb-cluster-0.x branch from 3dc3830 to 271afe4 Compare May 31, 2025 11:46

renovate-bot changed the title ~~Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.27.0~~ Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.30.0 May 31, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.30.0 #7

Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.30.0 #7

Uh oh!

renovate-bot commented Oct 23, 2023 •

edited by coderabbitai bot

Loading

v1.7.5

What's Changed

New Contributors

v1.7.5

What's Changed

New Contributors

what

why

references

Uh oh!

coderabbitai bot commented May 31, 2025 •

edited

Loading

Chat

Support

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (`.coderabbit.yaml`)

Documentation and Community

Uh oh!

Uh oh!

Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.30.0 #7

Are you sure you want to change the base?

Update Terraform github.com/cloudposse/terraform-aws-documentdb-cluster to v0.30.0 #7

Uh oh!

Conversation

renovate-bot commented Oct 23, 2023 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

what

what and why

what and why

🚀 Enhancements

what

why

references

🐛 Bug Fixes

what

why

references

🤖 Automatic Updates

what

why

References

what

why

references

🤖 Automatic Updates

what

why

references

what

why

references

what

why

references

🚀 Enhancements

v1.7.5

What's Changed

New Contributors

🤖 Automatic Updates

v1.7.5

What's Changed

New Contributors

what

why

references

what

why

references

what

why

references

🚀 Enhancements

what

why

references

🤖 Automatic Updates

what

why

what

why

what

why

what

why

what

why

what

why

what

why

what

why

what

why

references

what

why

references

renovate-bot commented Oct 23, 2023 •

edited by coderabbitai bot

Loading