Link SECRET_MANAGEMENT permission in v4 migration guide#137
Merged
nscuro merged 1 commit intoJun 6, 2026
Merged
Conversation
Point post-migration secret setup to the secret management section of the permissions reference. Signed-off-by: Valentijn Scholten <valentijnscholten@gmail.com>
valentijnscholten
force-pushed
the
link-secret-management-permission
branch
from
8b04a12 to
bd0cd52
Compare
nscuro
approved these changes
Jun 6, 2026
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.
Summary
SECRET_MANAGEMENTpermission is required to manage secrets after migration.Test plan
make buildpasses