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 could even make `pulumi.dynamic.Resource` generic and make it lift the generic type automatically, making it a more seamless experience to write dynamic providers, since you get to avoid duplicating your input type definition sprinkled with `pulumi.Input&lt;T&gt;`.

Sample of what an implementation could look like (simplified, doesn't support nested object, and isn't backwards compatible):

This sounds great! Could you file an issue?