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

Do you mean Pulumi Enterprise that can be deployed on prem (self-hosting) or custom backend (other than Pulumi Service, like GCS/S3 etc.)?

1) I have no idea since I haven’t been able to use that but I guess it should work the same as cloud version so yeah, it does control concurrency.
2) I think some locks were implemented (let me find it).

I’ve found this:
<https://github.com/pulumi/pulumi/pull/2697>

Not sure if it’s production-ready or not (I use Pulumi Service myself).

Thanks <@U0288KYUB7C>,  Yea I'm hoping to control execution of our pulumi with Temporal

<@U0366GFJSLR> you can't run multiple `up`s on the same stack within a project, you'll get a `409` status code

You can run lots and lots of stacks in a single project though, we have customers running thousands

<@UCWG26BH7> a stack has its own backend state right?

I was hoping to separate out certain parts of a project into different failure domains.

the locking is handled by your state storage in that case, so it depends entirely on how your state storage locking mechanism works

but in your case, you can separate out and use stack references, the reason we lock state is to ensure you don't have two updates clashing