This message was deleted.

Currently we expect providers to be written in go because we require them to be single file executables. We've got some internal prototypes to generate provider interface code for all the languages and to allow the providers to be npm packages, dotnet nuget libraries, python wheels etc.

Any ETA, or option to try these early stage prototypes? DMs are open. 🙂

I'm not sure, most of the team is at a planning event this week so someone might be able to say more about timelines (and if we're even taking this idea forward) next week. Won't be me though, I'll be on holiday 🏖️

Thanks a lot. Have a nice holiday. That sounds like I have to learn go, to make my own native provider. Very overwhelming but exiting as well.

Hello, I’m not sure to understand everything: if I’m right, the pulumi-eks and pulumi-awsx packages (not really providers?) are written in TS, but they are usable with Go since recent announcements. However, it seems necessary to have npm installed for it to work, though I didn’t see it documented (maybe I didn’t read attentively enough 😛). Did I misunderstood something?

There are on the component ressource level and not on a full provider level. I think 🤷