fix(rds): fix incorrect import/export combination check in AuroraMysqlEngineVersion.of() #33564
+2,648
−1
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.
Previously, AuroraMysqlEngineVersion.of() incorrectly determined whether import and export roles should be combined.
This caused inconsistent behavior when specifying engine versions manually using AuroraMysqlEngineVersion.of(...), leading to incorrect parameter settings in the DBClusterParameterGroup.
Issue #33562
Closes #33562
Reason for this change
The issue arises when specifying a custom Aurora MySQL version using AuroraMysqlEngineVersion.of(...).
The logic for determining whether import and export roles should be combined is incorrect.
It should be based on the major version.
This bug causes s3ExportBuckets to configure DBClusterParameterGroup incorrectly:
Description of changes
If the major version is not "5.7", _combineImportAndExportRoles is set to true
Describe any new or updated permissions being added
None.
Description of how you validated changes
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license