[db] Use a valid UUID for the admin user #15974
Merged
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
Use a valid UUID for the one-time admin user added by #15805.
A valid UUID is required for the admin user to able to interact with the public/server API to set up SSO.
See some internal discussion.
Related Issue(s)
Fixes #
How to test
kubectl port-forward deployment/server 9000:9000
curl -X POST localhost:9000/admin-user/login-token/create
https://<preview-domain>/api/login/ots/admin-user/:yourOtsKey
and visit it.It should now be possible to configure an OICD client (
Settings | OIDC
).Release Notes
Documentation
Build Options:
Experimental feature to run the build with GitHub Actions (and not in Werft).
leeway-target=components:all-ci
Run Leeway with
--dont-test
If enabled this will build
install/preview
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh