Hi! Are there any decision documents I can refer to when trying to understand why Pulumi defines its own string- and array-types?

https://www.pulumi.com/docs/intro/concepts/inputs-outputs/ This may help you understand why as well: https://leebriggs.co.uk/blog/2021/05/09/pulumi-apply Essentially it’s the same reason as the AWS SDK, the types are async in nature and because Go doesn’t have generics, we need a way to represent they’re eventual

Ah, so this approach may change with the recent introduction of generics?

Yes we’re investigating that at the moment

Excited to see what you conclude, will keep an eye on the blog 🙂