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

Hi Jeff,

Pulumi is licensed under the Apache 2.0 license so this is permitted, lots of customers use our product commercially. With regards to a UI that automates the CLI, we also encourage this, take a look at the automation API
<https://www.pulumi.com/blog/automation-api/>

Is there any published guide or reference on how to convert dynamic resources and providers to be fully fledged provider plugins?

Also, is it possible to keep the core provider plugin code written in typescript as it is today?

all pulumi's providers are written in Go, there isn't really a good plugin authoring guide unfortunately. If you're trying to convert a dynamic provider to a native provider, your best bet is to look at the kubernetes provider and go from there. We do need to improve here

Is there a justification for leaving it as a dynamic provider in typescript for now? E.g., is there a plan to offer support for writing full fledged providers in typescript? The APIs I’m calling all have good Sdks for nodejs. Go, not so much. 