-
Notifications
You must be signed in to change notification settings - Fork 12.8k
feat: secrets management admin UI #105953
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
feat: secrets management admin UI #105953
Conversation
Simple implementation (WIP) of UI with in-memory stubs.
Simple implementation (WIP) of UI with in-memory stubs.
…gement-admin-ui # Conflicts: # public/app/core/reducers/root.ts
API currently doesn't report back with a pending/progress state while a secret is being provisioned.
API currently doesn't report back with a pending/progress state while a secret is being provisioned.
…gement-admin-ui # Conflicts: # public/app/core/reducers/root.ts
`audiences` => `decrypters`
`audiences` => `decrypters`
- Also removed the possibility to enter custom values.
- Also removed the possibility to enter custom values.
…ui' into w1kman/secrets-management-admin-ui # Conflicts: # public/app/features/secrets-management/components/SecretForm.tsx # public/app/features/secrets-management/constants.ts
- invalid import (`@grafana/ui/`) - "missing" `Prop` export from `@grafana/ui/Input`
- update `fill` for delete button in `SecretItem` - turn off autocomplete for secret value
- add /admin/secrets to `api.go` - add/update translations - replace secret value input with textarea
- `SecretValueInput.tsx` - `SecretsSearchEmptyState.tsx` - `SecretList.tsx` - `SecretsEmptyState.tsx` - `SecretItem.tsx`
I'd missed the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
self-review attempt no.2 ✅
Hi @w1kman - I checked out the branch w1kman/secrets-management-admin-ui and created a couple of secrets. I noticed it changed the name after clicking create. Have you encountered this before? |
Yeah, if the name is empty, the backend will assign a random name. I will take a look. |
…gement-admin-ui # Conflicts: # public/app/core/reducers/root.ts # public/app/store/configureStore.ts
I've pushed a fix for the random name, as well as an update on handling secret updates and translation dependencies. |
Hi Thomas, I've completed testing on all the functionality of the page. This has been documented here: Grafana Secrets management UI - PR review Almost everything is working as expected! :) I have a couple of follow up items here:
|
- Delete secret modal: copy updated (see Miro). - Improve search filter interactions and capabilities - Improve name validation regexp (check last char to be alphanumeric) - Improve label.(name|value) validation regexp (check last char to be alphanumeric) - Add secure value limit (24kb)
The
I've talked to @macabu about this. 24kb seems to be the lowest limit (Azure) we need to support. I've updated the client validation for the |
…nto w1kman/secrets-management-admin-ui
…nto w1kman/secrets-management-admin-ui
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 2 weeks if no further activity occurs. Please feel free to give a status update or ping for review. Thank you for your contributions! |
Closing as stale! This moved! |
What is this feature?
UI for secrets management (see PR#97837)
Note: Client-side validation of form values (based on SecureValue spec)
Why do we need this feature?
For users to be able to create, read, update, and delete secrets.
Who is this feature for?
Currently, admin users only
Special notes for your reviewer:
To test, you can
make run
on this branch, with custom.ini settings:Considerations for further development:
createdBy/modifiedBy
(user id) (e.g. hardlink tousers/edit/<uid>
Please check that: