chore(rds): clusterScailabilityType is spelled wrong and should be clusterScalabilityType #32825
+288
−4
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.
Issue #32415
Closes #32415 .
Reason for this change
Misspelling of the
ClusterScalabilityType
type, enum, and prop.Description of changes
Deprecated misspellings of ClusterScailabilityType/clusterScailabilityType and aliased the misspelling for backwards compatibility. The misspelled name will be removed in the next MV release.
Describe any new or updated permissions being added
No permissions changes.
Description of how you validated changes
Added unit tests for the new spelling (ClusterScalabilityType/clusterScalabilityType), and kept unit tests that tested the misspelling.
Ran the relevant integration test.
# in packages/@aws-cdk-testing/framework-integ yarn integ test/aws-rds/test/integ.cluster-limitless.js
Ran Rosetta to verify README changes.
No complications from README changes in these commits.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license