[ADH-7956] Integration with Vault (Hashicorp/OpenBao) is implemented for storing sensitive configurations.#24
Merged
Conversation
… sensitive configurations.
… client; fix VaultClient._get_password_from_script
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.
What changes were proposed in this pull request?
The patch integrates HashiCorp Vault and OpenBao with the HUE configuration file processing logic. This allows the service to retrieve passwords, secrets, and other sensitive data directly from the KV v2 Vault secrets mechanism, instead of storing them in cleartext in configuration files.
Secrets are expected to be stored as
vault://<path>A configuration block for client configuration has been added. [desktop] [[vault]]
Authentication types supported