Add Deploy Tokens to the Credential Inventory
Release notes
Problem to solve
The credential inventory adds necessary visibility for compliance-minded organizations to know who or what has access to their GitLab systems and resources. It is missing a number of access credentials/tokens to provide a more comprehensive and reliable view of GitLab access and control of that access.
Intended users
User experience goal
An administrator should be able to view information about every Deploy Token in use within their instance.
Proposal
Add a Deploy Tokens tab to the credential inventory and list relevant information.
| Name | Username | Project | Creator | Created | Expires | Scopes | (Actions) |
|---|---|---|---|---|---|---|---|
| Test | gitlab+deploy-token-1 | Group / Project | ![]() |
Jan 13, 2021 | 20201-01-30 | read_repository, read_registry, write_registry | ![]() |
Empty state
| Preview |
|---|
|
No deploy tokens have been created yet. Deploy tokens allow access to packages, your repository, and registry images. |
Out of scope
Creating deploy tokens
Implementation plan
Total combined weight
backend
- When the Deploy Tokens tab is active, use the
DeployTokens::TokensFinderto find all tokens.
frontend update HAML and add a new empty state
- Add a new
Deploy tokenstab to the admin credentials inventory view. - When active and there are tokens, display the list of deploy tokens.
- Note: We can omit the
Creatoras there is no data stored for that. See #243825 (comment 836066838).
- Note: We can omit the
Empty state will be added in #351883.
Notes
Deploy tokens are already accessible on group-level. https://docs.gitlab.com/ee/user/project/deploy_tokens/#group-deploy-token


