docs: add decision record for HashiCorp vault authentication refactoring #4802
+81
−0
Conversation
This file contains 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
docs/developer/decision-records/2025-02-06-hashicorp-vault-authentication-refactor/README.md
Outdated
Show resolved
Hide resolved
docs/developer/decision-records/2025-02-06-hashicorp-vault-authentication-refactor/README.md
Show resolved
Hide resolved
ndr-brt
approved these changes
Feb 10, 2025
ronjaquensel
force-pushed
the
vault-authentication-dr
branch
from
1cb2e97 to
1c4df2d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR changes/adds
Adds a decision record about refactoring the HashiCorp vault implementation to support different methods of authentication.
Why it does that
At the moment, only one method of authentication is provided. This should be extensible to support the usage of HashiCorp vault in different deployments and setups.
Who will sponsor this feature?
me
Linked Issue(s)
Closes #4672
Supersedes #4720