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 a good place to start: <https://www.pulumi.com/docs/reference/pkg/>

All the Pulumi libraries are updated via language-standard methods (npm and that sort of thing) so you can just update whenever you feel like via `npm update` or equivalent. The binary plugins are updated automatically via Pulumi, you generally don't need to think about it.

Pulumi is updated frequently, several times a month. You can a notification at the command line when you use a version other than the latest, and you can choose when to update.

Thank you for sharing this! I'm interested in learning how fast the APIs are updated to reflect cloud providers' changes. How are these changes reflected in the roadmap? Any process around that? Is there a list of core services per cloud provider that are revised more often than others? 

For the "native" providers, they're almost instant (Azure-native; gcp-native (beta). The other large providers (esp. AWS) are fast; maybe a few days behind the equivalent terraform or SDK change. The smaller providers, I don't know, sorry.

The team are having a day off today, someone will be better able to help tomorrow, I'm sure.

You could look in the various github repos, it's all open source. <https://github.com/pulumi>

<@U012UJTT55M> Thanks for the great answers I had similar myself. I found this issue: <https://github.com/pulumi/pulumi-aws/issues/1535>

Is pulumi directly dependent on TF providers (all or some?)

our aws provider depends on the aws terraform provider, but we're working on a native provider

i expect the new version to be released today or tomorrow (cc <@UHTP242EB>

it'll be tomorrow as I am on vacation today :slightly_smiling_face: