Dynamic resource names based on release name

[fullmetal-fred]

Hey all!

Today when I was working on a Windmill migration, I found myself wanting to create 2 instances of Windmill alongside each other in the same namespace. Unfortunately I soon discovered that all of the resource names are static and not based on the helm release name, making 2 deployments in 1 namespace impossible. I could do this in two separate namespaces, but that would also require me to replicate secrets and other resources across those namespaces. It would be a lot simpler if the Windmill helm chart dynamically generated the resource names based on the helm release name, like name: {{ .Release.Name }}-app or name: {{ .Release.Name }}-windmill-app.

Make sense?

[rubenfiszel]

Good idea, we will just want to make sure it doesn't change the current names to avoid breaking changes but yes

[fullmetal-fred]

What if we used a value for resource base names for the name instead of using the release name? The default could be "windmill" which should meet the needs of existing deployments. But you could deploy a version and set it to "windmill-2" for example and get a whole deployment in parallel.