kctrl package repository release Should Allow Control of Image Tags

[nebhale]

Describe the problem/challenge you have
Currently, there is no way to control the image tags for created and published package repository imgpkg bundles. This prevents the creation of a package repository with a version that includes any build metadata, e.g. 0.0.1+git.c9cc39a

Describe the solution you'd like
The kctrl package repository release command should gain a --tag flag that is the equivalent of the kctrl package release command's --tag flag.

Anything else you would like to add:
Slack

---

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

[mamachanko]

@nebhale @praveenrewar This might be a duplicate of #1409

[nebhale]

They are related in the sense that they're both triggered by the same thing (the inability to use build metadata) but in detail they're different. My specific ask is for a flag to create parity between kctrl package release and kctrl package repository release and the other requests an automated mapping.

[devanshuVmware]

@nebhale Currently, the version provided by the user in the args is the added as image tag (or the unix timestamp if version is empty)
If I understand correctly, with this change, the user will be able to override that version tag by providing a user specific tag.
The image tag applied would take precedence in following order:

1. --tag
2. --version
3. unix time stamp

[nebhale]

@devanshuVmware Do you have to hand, the precedence for how the kctrl package publish works? I thought that --version wasn't included in that precedence hierarchy.

[devanshuVmware]

@nebhale Currently, the tag that is applied to the imgpkg bundle image is:
if --version flag is provided, apply it
else, add the unix timestamp as tag

with the introduction of --tag flag, I understand, its value should take precedence as tag, even if the user provides a value for the --version flag
if the --tag is not provided but --version is , then --version value will be used as tag,
if neither are provided, the default tag would be unix timestamp

[nebhale]

Yeah, I have no strong opinion other than consistency with the package behavior 😀. Looks like that's the path you're heading down.

[nebhale]

Validated this works as expected. Is there a regular release cadence for the project that I should expect this to fall into?

[devanshuVmware]

Validated this works as expected. Is there a regular release cadence for the project that I should expect this to fall into?

Thanks for validating it @nebhale !
The next release for KC is planned towards end of Jan. However, we can make an early release if you need it sooner.

[nebhale]

It’d be helpful to have it released earlier (we’d start using the new feature the first day it’s available) but at the same time, this isn’t make-or-break for us, so don’t kill yourself trying to get it out the door.