Skip to content

Link SECRET_MANAGEMENT permission in v4 migration guide #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nscuro merged 1 commit into from
Jun 6, 2026
+1 −0
Merged

Link SECRET_MANAGEMENT permission in v4 migration guide #137

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/guides/administration/migrating-from-v4.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -597,6 +597,7 @@ The staging schema is not portable across clusters and is not needed by v5 at ru
and turn the affected repositories back on.
See [Managing secrets](../user/managing-secrets.md) and
[Configuring secret management](configuring-secret-management.md).
A new [`SECRET_MANAGEMENT`](../../reference/permissions.md#secret-management) permission is required to manage secrets.
- Reconcile every user whose username got a `-CONFLICT-LDAP` or `-CONFLICT-OIDC` suffix
(delete genuine duplicates, rename legitimate external identities back to their original username).
- Wait a few hours, then verify that v5 has populated the `EPSS` table from the upstream feed.
Expand Down