https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
f
You should be able to override it with the name parameter and use an output. Then use simple string interpolation for the definition.
c
I know, but it leads to really ugly resource names.
I’m having to just use an integer, but it doesn’t really let you know what it’s for then.
Also, this does suck because if you want autonaming, you can’t.
f
Hmm I see yeah that’s fair. Maybe create a component resource if it’s a similar set of resources for each cluster? That way you could hide the ugliness 🙂
c
Not sure how that solves it? How am I supposed to use the cluster name from a stack reference?
I mean I would still need to do the component resource with a different value than the cluster name.
g
I think there's some pretty deep engine reasons why we can't support this currently. If you want to create an issue at pulumi/pulumi with your use case, could discuss the idea there.
c
The thing is, it doesn’t really make sense IMO from a user’s perspective. The resource already exists. It makes sense if I was trying to take a new resource and get a value as part of the resource name for something else (this scenario would be nice to support though), but this is an existing resource.
I’ll open up a ticket though. But yeah, this is a really frustrating part of pulumi, on top of all the double work that preview does before an apply, these would probably be my 2 biggest complaints.
g
Is there an issue for the "double work that preview does before an apply"? I'm not sure I'm following that one.
c
Apply should not have to recalculate anything. Preview takes forever as it is, and then apply has to redo all the logic.
pulumi up
should basically create a plan (preview) and execute it (apply)
Today they are rather disconnected.
g
Ah, got it. Yea, there is an issue for that one and is something we are planning to address.
c
Not sure of what the issue # is for the plan one, but hopefully that is sooner rather than later.
g
c
Thanks!
3 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