I’ve recently been creating a few Helm-charts for kubernetes, and whenever I create a new version of a chart, I create a tagged release/archive. Hence it is easy to target the correct chart-version when using helm, even if there are multiple charts in the same registry.
When I was writing Nomad-Packs, one of my issues was targeting/pinning different versions of the packs. I ended up with tagging each release with the pack+release, and then clone/download this version in the deployment-pipeline.
Are there plans to implement a similar “binary-release” model to Helm, targeting the “
metadata.pack.version” value? (Or are there any easier ways to target this version when deploying, that I have missed)
I want to deploy 2 packs from same registry, but the required versions are from separate git-commits. I need to pull the corresponding commit prior to deploying each pack.