Show that the container expiration policy is enabled
requested to merge 208269-container-registry-expiration-policy-notify-the-user-that-expiration-policy-is-enabled-and into master
What does this MR do?
This MR adds an alert in the container registry specifying that expiration policy is enabled and when the next run will be
Screenshots
| Type | Screenshot |
|---|---|
| Policy enabled + Images |  |
| Policy enable, no images |  |
| Policy disabled |  |
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [0] 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 #208269 (closed)
Edited by Nicolò Maria Mezzopera