Hello, I’m trying to deploy the same chart in two different clusters (in the same Pulumi project), but I’m having issue with naming: I can’t use the same Pulumi logical name for my two chart resources (else Pulumi complains about duplicate resource URN) and I didn’t find a way to override the release name used when templating the chart. Is it a deliberate choice to not let the user modify the release name (maybe I just didn’t see how to do it) or is it a missing feature which could be implemented (potentially by me when I’ve time)?

can you share your code?

I’ve this inside a component which is instantiated two times (once for each EKS cluster):

_, err = helm.NewChart(ctx, t.name+"-"+chartName,
		helm.ChartArgs{
			Path:      pulumi.String(path.Join(path.Dir(currentFile), "helm")),
			Namespace: t.Namespace.Metadata.Name().Elem(),
			Values:    values,
		},
		pulumi.Parent(t),
	)
	if err != nil {
		return errors.NewResourceCreationError("Helm chart", chartName, err)
	}

are you adding an index to the chart name? you need a unique urn for each

No, this is a constant (in fact, this is the name which I’d like to be used as the release name for the two charts templating). I’d like the chart deployment to be identical in the two clusters.

sorry I was focusing on this part of the problem:

else Pulumi complains about duplicate resource URN

duplicate urns are easy to fix, if you want to go down that path

Sure, the problem isn’t really the duplicate URN, it’s more that one can’t override the release name used during templating, it’s tightly coupled to the logical name, which I’d like to avoid.

I think we could consider adding a release name property, feel free to send a PR

Thanks, I don’t have time to do this myself right now, but I’ll see with my colleagues and I’m definitely adding it on my todo list 😉