Azure / Azure/acr-cli

Keep and Untagged seem to compound, is that intentional?

Open
#644 3 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
70
Forks
52
Avg merge
3d 2h
Merged PRs (30d)
12

Description

**Describe the bug**
First of all, not sure if this is a bug. But let me describe a scenario.

When you have a repository with 50 tags all linked to a single manifest (so 50 manifests) and you run purge on this 1 repository with "--keep 10 --untagged" and for simplicity lets say you set "--ago 0d".

Then purge would first untag 40 manifests, leaving you with 10 still tagged.
And after that, it would remove 30 of the 40 untagged manifests.

The end result being:
10 tags
20 manifests

**To Reproduce**
See description

**Expected behavior**
With the example above in mind, I somehow expected to end up with 10 tags and 10 manifests.
I'm just wondering if how it currently works is intentional or a byproduct of adding (the keep) functionality where this is a (happy) accident.

**Any relevant environment information**
- OS: Windows
- Version (acr-cli) 0.19

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.