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

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

i am not sure which class to subclass, do you have a short example <@U012UJTT55M>

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>

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

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>

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

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