Skip to content

feat: add --untagged-only flag for independent untagged manifest cleanup #489

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

balcsida
Copy link
Contributor

@balcsida balcsida commented Aug 8, 2025

Purpose of the PR

This PR introduces a new --untagged-only flag to the purge command, enabling users to clean up untagged manifests independently without affecting tagged manifests. This addresses the confusion and limitations reported in issues #480 and #486.

Changes

  • Added --untagged-only flag that exclusively targets untagged manifests
  • When --untagged-only is set, the --filter and --ago flags become optional
  • Users can now clean up all untagged manifests across all repositories or within specific repositories
  • Improved validation logic to prevent incompatible flag combinations

Usage Examples

# Delete all untagged manifests in all repositories
acr purge -r example --untagged-only

# Delete untagged manifests in specific repository
acr purge -r example --filter "hello-world:.*" --untagged-only

Breaking Changes
None. The existing --untagged flag behavior remains unchanged for backward compatibility.

Fixes #480 and #486

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Acr Purge --unttaged is targetting tagged manifests?
1 participant