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! Question regarding DIY backends... per the <https://www.pulumi.com/docs/iac/concepts/state-and-backends/#using-a-diy-backend|docs>, DIY backends offer stack locking features to prevent collisions during Pulumi upgrades. The wording implies that it is somehow inferior to the Pulumi cloud locking mechanism.
``` basic file-based locking system is enabled by default for all DIY backends.```
Anyone know what is "basic" about the DIY locking system exactly?

It’s “basic” because it’s  a simple local file-based locking mechanism. With Pulumi Cloud, it manages the locking and so prevents the risk of clobbering the lock.

I know that in the S3 backend, it puts an object in a `locks` directory and basically when that object exists, no other pulumi updates will succeed.  Deleting the object manually or `pulumi cancel` will allow you to update again.