Update Design of the Container Registry Cleanup Policy for tags
requested to merge 222885-update-design-of-the-container-registry-cleanup-policy-for-tags into master
What does this MR do?
This MR wires up the components created in: !47778 (merged) to achieve the desired UI and UX.
The Plan
Description | MR |
---|---|
Create a set of new components to implement the UI | !47778 (merged) |
Wire the new components and do UX and UI text reviews |
|
Refactor textareas to input fields, adjust toggle and next-run text | TBD |
Cleanup the shared folder and remove dead code |
TBD |
Screenshots (strongly suggested)
Empty state | Enabled State | Disabled State |
---|---|---|
Does this MR meet the acceptance criteria?
Screencapture
Desktop
Mobile
ExpirationPolicySettingsMobile
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines - [-] Merge request performance guidelines
-
Style guides - [-] Database guides
-
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers - [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec
- [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Related to #222885 (closed)
Edited by Nicolò Maria Mezzopera