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

image.png

I thought this argument, from the blog post <https://blog.gruntwork.io/why-we-use-terraform-and-not-chef-puppet-ansible-saltstack-or-cloudformation-7989dad2865c>  was no longer correct

Yes, no longer correct. I don't know about transactional checkpointing, but locking is now sorted for all backends.

State as a whole isn't encrypted, and I believe that's by design. Secret values are encrypted within the state. You can restrict access to the state in other ways, and anyone who can interact with the state (that is, anyone who can run Pulumi) can dump the state locally, so encrypting it in its normal location is moot.