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.

Pulumi Community

This isn’t possible no. If you need to explicitly name a resource in the upstream provider’s api, you can set the name property on that resource but the resource name itself has to be known at runtime 

That makes tooling around Pulumi rather hard to do

The current solution I’m investigating is wrapping Pulumi resources in a custom builder class that will eventually build the Pulumi resources but still leaves me access to the raw properties

I’m getting a sense from the questions you’re asking that you’re using Pulumi as an SDK, are you aware of the state/declarative model of Pulumi? The reason you cant use outputs as resource names is because if you do, the downstream resource can’t be created until the output is resolved, which breaks the dependency graph 

<@UCWG26BH7> I see. I’m not really trying to use Pulumi as a SDK. I guess what I’m trying to do is to build constructs around Pulumi. These constructs just encapsulates logic and configure the underlying resources. Do you think it is a bad pattern? 