Skip to content

feat/add node group configuration capability#67

Closed
waelghaith wants to merge 4 commits intoterraform-aws-modules:masterfrom
waelghaith:feat/add-node-group-configuration-capability
Closed

feat/add node group configuration capability#67
waelghaith wants to merge 4 commits intoterraform-aws-modules:masterfrom
waelghaith:feat/add-node-group-configuration-capability

Conversation

@waelghaith
Copy link
Copy Markdown

Description

  • Add node_group_configuration support for cluster‑mode replication groups and wire it through the wrapper.
  • Bump AWS provider minimum to >= 6.20.0 across root, modules, wrappers, and examples.
    Update terraform-docs outputs.

Motivation and Context

  • The AWS provider added node_group_configuration (>= 6.20.0) for cluster‑mode replication groups, needed for shard AZ pinning and slot ranges. The module didn’t expose this capability.
  • This support is required when restoring replication groups from snapshot_arns, since AWS requires node_group_configuration (including slots) for that workflow.

Breaking Changes

  • AWS provider minimum is now >= 6.20.0.
  • preferred_cache_cluster_azs default changed from [] to null (argument omitted by default).

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@waelghaith waelghaith changed the title Feat/add node group configuration capability feat/add node group configuration capability Jan 29, 2026
@waelghaith waelghaith closed this Jan 29, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 1, 2026

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant