Skip to content

fix: conditionally include SnapshotRetentionLimit and add SnapshottingClusterId#1

Open
aaronwalker wants to merge 3 commits into
masterfrom
fix/snapshot-retention-novalue
Open

fix: conditionally include SnapshotRetentionLimit and add SnapshottingClusterId#1
aaronwalker wants to merge 3 commits into
masterfrom
fix/snapshot-retention-novalue

Conversation

@aaronwalker
Copy link
Copy Markdown
Member

SnapshotRetentionLimit was unconditionally passed as a Ref. When empty, CF threw Integer type validation errors. Also adds SnapshottingClusterId support (required when enabling SnapshotRetentionLimit). Both use AWS::NoValue when empty, leaving manual config untouched.

Aaron Walker added 3 commits April 27, 2026 12:20
…gClusterId support

SnapshotRetentionLimit was unconditionally passed as a Ref, causing
Integer type validation errors when the parameter was an empty string.

Now uses AWS::NoValue when empty, leaving manual backup config untouched.

Also adds SnapshottingClusterId parameter (required by ElastiCache when
enabling SnapshotRetentionLimit via CloudFormation).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant