#397 Adding a note for sensitive values #398
Merged
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
Adding a blurb instructing the user how to configure and secure values with sensitive information.
|
Fixes #397 |
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.
Description
This pull request includes an update to the
docs/configuration.mdfile. The change adds a new section on handling sensitive data in the Tapir configuration.The most significant change is:
docs/configuration.md: Added a new section, "Note Regarding Sensitive Data", providing guidance on how to handle sensitive data like keys, passwords, connection strings, etc. The update recommends using a secret manager like AWS Secrets Manager or Azure Key Vault, and provides information on using Opaque Kubernetes Secrets for users operating in a Kubernetes environment.Type of change