Add cleanup status field to graphQL ContainerRepositoryType
🌴 Context
In !44926 (merged), we added a graphQL API to get container repositories from a given Group or Project.
Parallel to that, in !40740 (merged) we added limits and throttling to cleanup policies. We will not go into the details of that but the important part is that a new field has been added to the ContainerRepository model: expiration_policy_cleanup_status.
This field is an enum that simply describe the state of the tags cleanup process on the given container repository.
This MR will unblock the frontend work of #276900 (closed).
🔍 What does this MR do?
This MR aims to add the expiration_policy_cleanup_status field to the ContainerRepositoryType.
- Adds the new field to the related graphQL type
- Update the related specs. They are two of them:
- One for the list container repositories graphQL api
- One for the get container repository details graphQL api
📷 Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
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