Transfer Chocolatey Repos to Carvel

[cari-lynn]

This issue is to track transferring the Chocolatey repositories from their current home in adriens GitHub to a single repository in the vmware-tanzu org. This applies to ytt, imgpkg, kbld, kapp, and vendir.

This issue has a discussion on steps to get the repos transferred. Quoted below:

The current thinking is:

1. We create a repository in vmware-tanzu called carvel-chocolatey-packages
2. The separate chocolatey repos you're maintaining now are pull requested in (this helps us for legal reasons relating to the CLA)
3. You will be added to the repository as a maintainer
4. We will add or accept contributions adding automation to the specific tooling repos that will trigger on release and commit and push an update to the chocolatey repo.

[cari-lynn]

The current state of this work is blocked on approval for the new repo carvel-chocolatey-packages. This can unfortunately take some time, and we believe that the approval will start to move forward when people are back from time off later this week. @DennisDenuto and I are keeping an eye on its progress.

Huge thanks to @adriens for your patience and effort with this move!

[adriens]

Hi guys, no worry. For now, all packages have been automated and then, do not require me much effort to follow releases on each Carvel tool... even when the weeks are very busy.

My major concern now is that I really love to link a chocolatey release (or more generally any software release) to a GH release/tag. I really love that approach. To be totally honest with you I'm afraid to loose that if we put all of them in a same repo, except if we provided a kind of Carvel bundle (as a zip) with a meta-version. Then that would be quite satisfying even if most of the time few tools in the bundle may be upgraded.

[cari-lynn]

Hey @adriens! Great to hear that all packages have been automated 😎

I really love to link a chocolatey release (or more generally any software release) to a GH release/tag

I am wondering how you link the chocolatey release to a github release. Specifically, what do you use the chocolatey release for? Is it to keep track of the state of the chocolatey repo at a specific version or another reason?

I wonder this because I think there may be another way to track that information, such as tagging a commit that updates the ytt.properties file.