feat(redshift): supports excludeCharacters settings for DatabaseSecret #30563
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 # (if applicable)
Closes #26847.
Reason for this change
In the case of passwords generated by DatabaseSecret, there may be a need to exclude certain characters.
The original issue was to exclude the backtick character from passwords.
However, the current default value of
excludeCharacters
,'"@/\ ''
, matches the characters that are not supported in Redshift (docs).Instead of including the backtick in the default value of
excludeCharacters
, it was considered appropriate to make it configurable.Description of changes
Add
excludeCharacters
property to specify characters to not include in generated passwords.Description of how you validated changes
Add unit tests and integ tests.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license