Deploy keys credentials inventory - frontend
Problem to solve
Compliance-minded organizations require insight into the access individuals have to their systems. We're launching an inventory of PAT and SSH credentials in %12.6, which begins to provide this insight to customers. Missing still is Deploy Keys
so that customers can have a more holistic view of access to their GitLab environment.
Intended users
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ -->
Further details
This is an iteration to add Deploy Keys
to an existing credential inventory accessible by Administrators
.
Proposal
Add Deploy Keys
to the credential inventory.
Title | Fingerprint | Read-only access | Read-write access | Created | (Actions) |
---|---|---|---|---|---|
Admin deploy key | d2:e8:be:cf:fd:a7:b4:fd:a7:b4 |
2 projects | 1 project | 20201-01-01 | ![]() |
Empty state
Preview |
---|
illustrations_empty-state_empty-deploy-keys-lg.svg](https://gitlab.com/gitlab-org/gitlab-svgs/blob/main/illustrations/empty-state/empty-deploy-keys-lg.svg) Deploy keys allow read-only or read-write (if enabled) access to your repository Deploy keys can be used for CI, staging or production servers. You can create a deploy key or add an existing one. ![]() |
Permissions and Security
Only Administrators
can view this information within the Admin Panel
Implementation plan
- Add deploy keys tab to
ee/app/views/shared/credentials_inventory/index.html.haml
- Add
New Deploy Key
button to tabs list when viewing deploy keys - Create deploy keys HAML view in
ee/app/views/shared/credentials_inventory/deploy_keys/...
- Add deploy keys delete modals
- Add tests
- Add QA tests
Note that the empty state will be added in #351883.