[Secrets] Add a section to give the best pratices for accessing secrets in a service#21865
Open
tcoch wants to merge 1 commit intosymfony:6.4from
Open
[Secrets] Add a section to give the best pratices for accessing secrets in a service#21865tcoch wants to merge 1 commit intosymfony:6.4from
tcoch wants to merge 1 commit intosymfony:6.4from
Conversation
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
2 participants
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.
Last week I was wondering what was the best way of handling this subject, and couldn't find the answer (though I found multiple ways of doing it with different technical approches).
I propose this PR to document this way of accessing secrets values inside a service, as the 'best pratice' if this is in fact agreed upon.