You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a use case where I have a monorepository of helm charts that are being managed by different version cadences. I would love it if there was a way to prefix my tags in such a way as to keep that cadence when a specific tag needs updating. For example, in a repository with the following folders:
charts cluster-addons
I could run separate github actions for each of these folders, and have prefixes for the tags like so:
charts-0.1.0 cluster-addons-0.1.0
This is just an example, I am aware helm has its own versioning infrastructure built-in. But I have a use case where I am bootstrapping EKS clusters with various charts managed by helm, and I do not wish to deepen my helm chart hierarchy one level down just for versioning as that is a bit heavy handed.
The text was updated successfully, but these errors were encountered:
I have a use case where I have a monorepository of helm charts that are being managed by different version cadences. I would love it if there was a way to prefix my tags in such a way as to keep that cadence when a specific tag needs updating. For example, in a repository with the following folders:
charts
cluster-addons
I could run separate github actions for each of these folders, and have prefixes for the tags like so:
charts-0.1.0
cluster-addons-0.1.0
This is just an example, I am aware helm has its own versioning infrastructure built-in. But I have a use case where I am bootstrapping EKS clusters with various charts managed by helm, and I do not wish to deepen my helm chart hierarchy one level down just for versioning as that is a bit heavy handed.
The text was updated successfully, but these errors were encountered: