This message was deleted.

sparse-intern-71089

10/13/2020, 8:09 PM

This message was deleted.

happy-pencil-64085

10/13/2020, 8:09 PM

I could set the resources to have static names, but I'd rather use the dynamic ones so I don't run into collision issues

little-cartoon-10569

10/13/2020, 8:10 PM

Assuming your SDK code is dependent on Pulumi code, you'll need to run it in an

Output.apply()

that's dependent on the resource that Pulumi creates. Or, you could use automation-api, that might make the structure a little easier to read.

worried-city-86458

10/13/2020, 8:16 PM

Automation api is not available for dotnet/c#... yet

worried-city-86458

10/13/2020, 8:18 PM

A dynamic provider might be the way to go, but those are also currently not supported for dotnet/c#

little-cartoon-10569

10/13/2020, 8:18 PM

Yep, so the apply route might be best. But if you wanted to write a small nodejs or golang wrapper around your C# pulumi code... actually, might as well write two C# apps at the point, and call both from a script...

little-cartoon-10569

10/13/2020, 8:19 PM

Not elegant, but certainly easy..

happy-pencil-64085

10/13/2020, 10:32 PM

gotcha thanks!

6 Views

Open in Slack

Previous Next

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.