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

Could this be the rival to the extremely expansive libraries of AWS CDK that we've been waiting for??  (oodles of pre-written, well-tested components that solve common problems) Or is that more what `awsx` is about?

Yes, it could be, but we don't limit ourselves to just AWS. :wink:

Cool, is this something like: <https://galaxy.ansible.com/>

That would be awesome

<@U030L46M92L> not exactly. The counterpart of Ansible Galaxy for Pulumi is the <https://www.pulumi.com/registry/|Registry>. If I take Puppet as a product to make an analogy. It also had a place to find out about things which already existed: <https://forge.puppet.com/|Puppet Forge>. This place contains modules coming from Puppet Inc, as well as numerous contributors. But when you have OSS contributions, it happens that someone’s interest to maintain own work goes away. If you have users of your work, you would rather have other people pick up the maintenance. That’s where a community effort can step in. For Puppet, that is <https://voxpupuli.org/|Vox Pupuli>, for Pulumi it is <https://github.com/pulumiverse|Pulumiverse>. The result of our shared efforts will still be published to the Pulumi Registry for easy discovery.
Hope this clarifies it a bit more.

is this blog getting promoted on the Pulumi Linkedin profile?

the blog post mentioned knative but I don't see npm packages published, and I got parsing error when I ran crd2pulumi myself. Is this related to that "dash character in property name" issue?

<@U010RQ505HT> indeed, dashes aren't handled very well. We're making improvements to crd2pulumi and our CRD coverage will grow as we do :+1:

Hi, any news on dashes in the name issue?