Allow PostgreSQL single user rotation on databases with restricted password management #50
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 available: n/a
Description of changes:
When a RDS PostgreSQL instance is configured with restricted password management, only users member of
rds_password
role are allowed to change passwords. Setting this permission to any role grants permission to manage passwords in all roles, which might not be desirable.With the changes added on this feature, the
masterarn
field that is already used by the Multi User Rotation function can also be used in the Single User Rotation function. If this field is exists in the secret, then the Master user is used for setting the new password in the database. Otherwise, the user tries to change its own password.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.