#3135 RFE: add --explain argument to list-tagged
Opened 2 years ago by ktdreyer. Modified 2 years ago

When users run koji list-tagged --inherit --latest <tag> <package> on a tag with many parents, it is not immediately obvious how Koji chose the "latest" ​build. It can be confusing to understand what is going on when one parent with a high priority has an older NVR than a parent with a lower priority.

Please consider adding a --explain flag to list-tagged that would give a human readable description, like:

Build X is tagged in Y tag because <user> tagged it into into Z tag on <timestamp>

Maybe with pointers to koji list-history and koji list-tag-inheritance as well.

While I'm all for helping users understand what Koji is doing, I'm not sure the proposed output will help much. It might be better to provide a clear doc and link it in the usage text.

Metadata Update from @mikem:
- Custom field Size adjusted to None

2 years ago

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.28
- Issue tagged with: doc

2 years ago

This user suggestion came from another user actually.

I suspect that person was thinking of how kubectl explain provides some built-in help for the various resources in a cluster.

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.29 (was: 1.28)

2 years ago

Metadata Update from @tkopecek:
- Issue set to the milestone: None (was: 1.29)

2 years ago

Login to comment on this ticket.

Metadata