Repository navigation
fix(E3026): skip NumCacheClusters check for cluster mode groups sized by NodeGroupConfiguration or ReplicasPerNodeGroup - #4920
Merged
kddejong merged 1 commit intoNov 2, 2026
Conversation
Contributor
Author
|
Hi maintainers, the workflow runs on this first-time contributor PR are waiting on approval. Could someone approve them when you get a chance? Thanks. |
kddejong
approved these changes
Nov 2, 2026
… by NodeGroupConfiguration or ReplicasPerNodeGroup Fixes aws-cloudformation#4856 Signed-off-by: Varshith Puli <pulivarshit@gmail.com>
kddejong
force-pushed
the
fix-4856-e3026-cluster-sizing
branch
from
November 2, 2026 23:26
debc704 to
0e0717c
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4920 +/- ##
=======================================
Coverage 94.74% 94.74%
=======================================
Files 442 442
Lines 16145 16149 +4
Branches 3138 3140 +2
=======================================
+ Hits 15296 15300 +4
Misses 469 469
Partials 380 380
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #4856
E3026 reported
"NumCacheClusters" must be greater than onefor cluster modeAWS::ElastiCache::ReplicationGroupresources wheneverNumNodeGroupswas unset, even when the group was sized another way. Both templates in the issue deploy cleanly on CloudFormation, so these are false positives.The CreateReplicationGroup API reference says of
NumCacheClusters: "This parameter is not used if there is more than one node group (shard). You should use ReplicasPerNodeGroup instead." When a cluster mode group setsNodeGroupConfiguration, its shards are defined explicitly, and when it setsReplicasPerNodeGroup, it is sized in cluster mode terms. In both casesNumCacheClustersdoes not apply, so the check now skips those groups. TheAutomaticFailoverEnabledcheck in the same rule is untouched, and groups with none ofNumNodeGroups,NodeGroupConfiguration, orReplicasPerNodeGroupare still reported exactly as before.Changes:
CacheClusterFailover: skip theNumCacheClusterscheck whenNodeGroupConfigurationis set orReplicasPerNodeGroupis present.NodeGroupConfigurationand a one shard group sized byReplicasPerNodeGroup, mirroring both templates in the issue.Verification:
test/unit/rules/resources/elasticache/: 14 passed.test/unit/rules/resources/: 1353 passed.cfn-lint --regions us-east-1with no findings.