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

So prevents concurrent modification like that 

<@UB8A66MPS> thanks. So just one person can modify the whole environment ? That is fair enough ... So why the `Remote state` is being introduced in one of recent PRs ?

Can't pulumi save its state in remote location ?

&gt; it doesn’t: it locks entire stacks
remote state with s3, at least, doesnt lock (yet), there are other discussions about adding locking.  (if I recall).

using pulumi's saas for your backend you do get locking by default.  I dont know about the state of other backends for locking.

That is true: my answer is scoped only to using the pulumi service either in hosted SAAS or a private version

The state can be saved remotely but it does not lock right now - I believe there is an open issue for that