https://pulumi.com
Join Slack
This message was deleted.
# kubernetes
s
This message was deleted.
b
can you share your code?
b
I’ve this inside a component which is instantiated two times (once for each EKS cluster):
Copy code
_, 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)
	}
If I remove the 
t.name
prefix, I get the duplicate error issue, but with it, all the resources deployed by the chart have 
t.name
prefix in their name.
b
are you adding an index to the chart name? you need a unique urn for each
b
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.
b
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
the release name is 
t.name+"-"+chartName
so you can override it if you wish
but yes, the logical name = release name
b
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.
OK, so is there a technical reason behind this tight coupling or would you allow a PR to add the ability to change the release name (kind of physical name)?
b
I think we could consider adding a release name property, feel free to send a PR
b
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 😉
Hello @billowy-army-68599, I finally couldn’t resist having a look at it and came up with small change to start with: https://github.com/yann-soubeyrand/pulumi-kubernetes/commit/b405b9f49c24775e6b33f52d4d0ceb3b8bf94369 From now on, I don’t know exactly what to do: I tried 
make build
and it gave me a working Go SDK, but I’ve errors about Java (the requirements for Java aren’t indicated in the 
CONTRIBUTING.md
file) and I get a lot of space differences in the Go SDK files which seems strange. Can you give me hint please?
6 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by