GH-920 Handle duplicate database roles#954
Open
goutamadwant wants to merge 1 commit into
Open
Conversation
Use distinct database secret backend metadata names when the same Vault database role is mapped to different target username and password properties. Fixes spring-cloudgh-920 Signed-off-by: Goutam Adwant <workwithgoutam@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
spring.cloud.vault.databasesentries with the same backend and role to contribute separate datasource credential properties.Fixes gh-920
Testing
git diff --check./mvnw -pl spring-cloud-vault-config-databases -Dtest='*UnitTests' test