Container Registry UI - Expand missing digest UI to better inform the user
Problem to solve
Currently, when an image tag is missing manifest digest information, we're implementing a small warning flag with a tooltip. #227558 (closed)
This is an improvement from blank information but lacks robust information to help aid our users to resolve issues with the tag.
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Sam (Security Analyst)
- Rachel (Release Manager)
User experience goal
Explicitly tell the user the status of the errored image tag and provide actionable steps to investigate.
Proposal
Expand the UI response to this error to include an expandable area that spells out the error and provides a link directly to documentation to help resolve this issue.
| More robust solution |
|---|
![]() |
Further details
Permissions and Security
Documentation
We would need to add a section to the documentation explaining what it means to have a missing manifest digest, and ways to resolve the situation.
Availability & Testing
What does success look like, and how can we measure that?
When a user encounters a tag with a missing digest, they can understand the situation and resolve things.
What is the type of buyer?
Is this a cross-stage feature?
No
