-
Notifications
You must be signed in to change notification settings - Fork 40
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.
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
[feature] Add Omni URL to add service account create screen #858
Comments
Unix4ever
added a commit
to Unix4ever/omni
that referenced
this issue
Jan 23, 2025
Fixes: siderolabs#858 Signed-off-by: Artem Chernyshev <[email protected]>
Unix4ever
added a commit
to Unix4ever/omni
that referenced
this issue
Jan 23, 2025
Fixes: siderolabs#858 Signed-off-by: Artem Chernyshev <[email protected]>
Unix4ever
added a commit
to Unix4ever/omni
that referenced
this issue
Jan 23, 2025
Fixes: siderolabs#858 Signed-off-by: Artem Chernyshev <[email protected]>
Unix4ever
added a commit
to Unix4ever/omni
that referenced
this issue
Jan 23, 2025
Fixes: siderolabs#858 Signed-off-by: Artem Chernyshev <[email protected]>
Unix4ever
added a commit
to Unix4ever/omni
that referenced
this issue
Jan 24, 2025
Fixes: siderolabs#858 Signed-off-by: Artem Chernyshev <[email protected]>
Unix4ever
added a commit
to Unix4ever/omni
that referenced
this issue
Jan 27, 2025
Fixes: siderolabs#858 Signed-off-by: Artem Chernyshev <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Description
If users create a service account via the CLI they are shown output for the service account key and omni endpoint so they can easily consume that information in their config. In the web UI they are only shown the key.
Solution
We should add a copyable field in the web UI so they can easily copy the correct URL for the omni instance to be used in their configuration.
This is helpful in product integrations such as Portainer.
Alternative Solutions
We could add a note about the URL so they make sure they use the correct endpoint which is different than the API endpoint shown on the home screen.
Notes
No response
The text was updated successfully, but these errors were encountered: