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

This is indeed as intended. The reason is due to the lack of generics in Go. Due to the async nature of the cloud, we model a given input to a cloud resource as `Input&lt;T&gt; = T | Output&lt;T&gt;` where T is your plain string type, and `Output&lt;T&gt;` is a future/promise that will eventually produce a T.

In languages like Typescript and C#, we can use generics to represent this and allow using native types. In go we have to create this custom `pulumi.String` `<http://pulumi.Int|pulumi.Int>` etc, to work around this.

If you'd like a high level overview I recommend watching this: <https://www.crowdcast.io/e/2020-04-14-PNW-Go>

or <https://www.youtube.com/watch?v=s91qF5MLy14&amp;t=10s>

we found the async nature in TS very hard to work with at times…

It would be really nice if this could be abstracted out… but easier said than done I suppose

that video is super helpful - thx for sharing

Agreed, the async nature can be a little bit of a mind bender.

Definitely a learning curve, but it is very powerful and enables much faster deployments through parallelization than would otherwise be possible.