Add `force`, `noprune` option to `PurgeImages` GQL API
- Dominant language
- Python
- Stars
- 670
- Forks
- 183
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 368
Description
## Motivation
- When the administrator runs "purge images," there may be cases where certain options need to be used.
## Required Features
- The `purge images` CLI command and GQL arguments will include the `force` and `noprune` options.
## Impact
- The administrator will be able to modify these options when running the `purge images` command.
## Testing Scenarios
- For example, when calling `purge images` on an image that is currently in use, an error occurs because the default value of the `force` option is `False`, preventing the image from being deleted.
Check that when the `force` option is set to `True`, the error does not occur and the in-use image is deleted immediately.
JIRA Issue: BA-820
Contributor guide
Research direction
Locate the `purge images` CLI entry point and the `PurgeImages` GQL API definition, then trace how their arguments are handled and where related tests live. Add support for `force` and `noprune` in both interfaces, and verify that enabling `force` permits deletion of an in-use image without an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, graphql, python
- Domain
- api, backend-api-design, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100