chore(deps): update terraform cloudposse/elasticache-redis/aws to v1.9.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/elasticache-redis/aws (source)	module	minor	1.7.0 -> 1.9.1

---

Release Notes

cloudposse/terraform-aws-elasticache-redis (cloudposse/elasticache-redis/aws)

v1.9.1

Compare Source

🚀 Enhancements

bump aws provider version to support valkey engine on other resource types @​joe-niland (#​257)

what

• Update AWS provider version to 5.73.0

why

• When specifying valkey in the engine version, the apply fails because this engine value is not supported on the aws_elasticache_replication_group resource

references

• None

v1.9.0

Compare Source

248 - Fix planning failure @​rtisma (#​254)

what

• terraform plan does not error out now when the module is disabled.

why

• skip coalescing null values when the module is disabled
• applies only to local.endpoint_address and local.reader_endpoint_address

references

closes #​248

v1.8.0

Compare Source

[FEAT] add `global_replication_group_id` support @​miguelzenteno (#​253)

what

• adds support for the global_replication_group_id attribute
• updates code to set other attributes to null when global_replication_group_id is set.

why

• We want to use elasticache_global_replication_group along side this module to manage global datastores
• When this attribute is set, the cluster will be set as a secondary for the global datastore

references

• https://registry.terraform.io/providers/hashicorp/aws/5.86.0/docs/resources/elasticache_global_replication_group

v1.7.1

Compare Source

feat: add snapshot_arns_to_restore for serverless ElastiCache @​muhammadasgharaliqureshi (#​252)

What & Why

• Adds a new variable serverless_snapshot_arns_to_restore that allows restoring a serverless ElastiCache Redis cluster from an existing snapshot.
• References Issue #​251
• This capability is essential for users migrating from a serverful Redis cluster to serverless via snapshot restore.

References

• AWS ElastiCache Serverless Documentation
• Terraform Resource: aws_elasticache_serverless_cache

Example Usage

module "redis_serverless" {
  source  = "cloudposse/elasticache-redis/aws"

### existing variables ...
  serverless_enabled                  = true
  serverless_snapshot_arns_to_restore = ["arn:aws:s3:::my-snapshot-bucket/redis-snapshot.rdb"]
}

Testing

• Ran terraform validate on the module; no errors.
• Executed terraform plan using the examples/ folder with this new variable set, and verified it passed.
• Confirmed that when specifying serverless_snapshot_arns_to_restore, the argument is included in the aws_elasticache_serverless_cache.default resource.

Testing Results

tofu init

tofu plan

Checklist

• Added new variable serverless_snapshot_arns_to_restore in variables.tf
• Updated aws_elasticache_serverless_cache.default in main.tf to pass the variable
• Documented usage in the README (or relevant doc files)
• Passed terraform fmt and terraform validate
• Awaiting maintainer feedback

closes #​251
fixes #​251

🤖 Automatic Updates

chore(deps): update terraform cloudposse/dynamic-subnets/aws to v2.4.2 @​[renovate[bot]](https://redirect.github.com/apps/renovate) (#​221)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/dynamic-subnets/aws (source)	module	patch	2.4.1 -> 2.4.2

---

Release Notes

cloudposse/terraform-aws-dynamic-subnets (cloudposse/dynamic-subnets/aws)

v2.4.2

Compare Source

🚀 Enhancements

chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​&#​8203;renovate (#&#​8203;191)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/utils/aws (source)	module	minor	1.3.0 -> 1.4.0

---

Release Notes

cloudposse/terraform-aws-utils (cloudposse/utils/aws)

v1.4.0

Compare Source

Add il-central-1 region @​&#​8203;&#&#​8203;8203;jasonmk (#&#&#​8203;8203;31)

what

Add new Tel Aviv (il-central-1) region

why

Provide full coverage

references

Sync github @​&#​8203;&#&#​8203;8203;max-lobur (#&#&#​8203;8203;27)

Rebuild github dir from the template

---

🤖 Automatic Updates

chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​&#​8203;renovate (#&#​8203;191)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/utils/aws (source)	module	minor	1.3.0 -> 1.4.0

---

Release Notes

cloudposse/terraform-aws-utils (cloudposse/utils/aws)

v1.4.0

Compare Source

Add il-central-1 region @​&#​8203;&#&#​8203;8203;jasonmk (#&#&#​8203;8203;31)

what

Add new Tel Aviv (il-central-1) region

why

Provide full coverage

references

Sync github @​&#​8203;&#&#​8203;8203;max-lobur (#&#&#​8203;8203;27)

Rebuild github dir from the template

---

Update README.md and docs @​&#​8203;cloudpossebot (#&#​8203;189)

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

---

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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

---

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 this update again.

---

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

---

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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 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? Join our Discord community 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 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.

[mergify]

/terratest

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Require terratest

Wonderful, this rule succeeded.

This rule require terratest status

• check-success = test/terratest

[gberenice]

/terratest

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

/terratest

[github-actions]

There are no real tests for this component. So we set terratest statuses to successful execution without running any tests

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟠 Require terratest

Waiting checks: test/terratest.

This rule require terratest status

• check-success = test/terratest

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

/terratest

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

/terratest

[github-actions]

These changes were released in v1.535.3.