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

It would help even more with Kubernetes types used to express yaml equivalents... just need to improve the Pulumi C# types.
What do you reckon, <@UB39JFCKC>?

Yeah… We can’t get rid of input types I’m afraid.

I'm not suggesting that, rather they should somehow play nice with target typing, probably by having a default ctor but I'm not sure of the implications.

The default constructor isn’t enough, right? The generic type doesn’t have the properties that you set. Compiler should somehow be instructed to instantiate the `T` type directly, not `Input&lt;T&gt;`

Yeah I think you're right. The `Input&lt;T&gt;` is relying on implicit type conversion. The thing is you only ever instantiate `T` directly, otherwise you're passing an `Output&lt;T&gt;` from upstream.

I can't see an easy way to do it since `Input&lt;T&gt;` can't derive from `T`, so it would have to compose / wrap `T` instead, effectively lifting the properties of `T`. That would require either dynamic dispatch or code generation.

We do a similar codegen for Go, so it is possible, but I’m not sure if it would be a good thing for C#. Go doesn’t have generics, so options are limited.

IIRC the typescript support lifts properties, which is nice to have as it makes `apply` etc go away.

TypeScript has a language feature for that