👋 hello! Is there any way around or a rationale for requiring that resource definitions use the Pulumi types instead of native types? For example, in the below example from the docs, is there a way to use a regular string for the value of the

Protocol

option?

Maybe it's not explained well in the docs, but basically

Protocol

there is an

Input

- which can be either an

Output

of another resource or a plain string. If you were to use a native type like

string

it wouldn't have information about the above. Having said that, https://github.com/pulumi/pulumi/discussions/13057 is getting there, it's already in Pulumi 3.80 and it's amazing!

It’s worth pointing out that’s just the core support without any provider implementation but nonetheless a great step forward

Ah ok thanks for the context! So the Pulumi types are basically lifting wrappers to get the async stuff to work?