Hey all, trying to understand the self-managed state. I'd use either a GCS or S3 bucket. Does Pulumi handle locking/concurrency on these types of backends automatically? The documentation isn't really clear, and seems to suggest only the Pulumi Service backend does this. If we had GCS/S3 backend could we end up with a broken state if a stack was updated by 2+ instances concurrently? Thanks!
03/10/2023, 9:28 PM
yes it does, it’s handled by the state store itself
the bucket has object locking, so pulumi writes a file for each update