This message was deleted.

sparse-intern-71089

01/01/2022, 3:50 AM

This message was deleted.

little-cartoon-10569

01/03/2022, 7:47 PM

You should subclass that, and pass in your own type string as the 2nd parameter to the constructor

some-church-49045

01/06/2022, 12:13 AM

i am not sure which class to subclass, do you have a short example @little-cartoon-10569

little-cartoon-10569

01/06/2022, 12:18 AM

I can't find one in the examples repo. Here's one from the docs: https://www.pulumi.com/docs/intro/concepts/resources/#authoring-a-new-component-resource

little-cartoon-10569

01/06/2022, 12:19 AM

It's a single-line example, but that's because it really is that simple...

little-cartoon-10569

01/06/2022, 12:20 AM

That example is for a component resource, but the same applies to resources created by dynamic providers. E.g.; https://www.pulumi.com/docs/intro/concepts/resources/#dynamic-resource-inputs

little-cartoon-10569

01/06/2022, 12:25 AM

Aha! Found an actual example: https://github.com/pulumi/examples/blob/9cb12a7fac28f229fb73736e197a85264ff12b7c/classic-azure-ts-dynamicresource/cdnCustomDomain.ts#L301

little-cartoon-10569

01/06/2022, 12:26 AM

The

pulumi.dynamic.Resource

class is subclassed, and the 2nd parameter (name) is where the type info goes (line 301). Not sure why it was done this way, instead of with a type and name like in component resources...

some-church-49045

01/08/2022, 9:15 PM

that's awesome!!! thks @little-cartoon-10569

👍 1

48 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.