Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Title
s
sparse-student-54516
11/10/2021, 3:21 PMFor storing state file of my pulumi stack I am using s3 bucket. Should I use single s3 bucket for all stacks/env? or should I create 3 different buckets for state file of 3 different stacks?
Which is better/preferred? Our aim it to keep state file of different env as isolated as possible.
Please suggest.
l
little-cartoon-10569
11/10/2021, 8:23 PMNow that you can get Pulumi to lock state during deployments, it is best to use one URL for all projects that are able to access each other via StackReference.
There is a risk of collision when two projects share a single unlocked backend (S3 bucket URL), but that's mitigated by Pulumi's locking.
And you cannot use StackReferences between projects with different backend URLs.
s
sparse-student-54516
11/12/2021, 9:48 AMthanks @little-cartoon-10569, We have decided to go with different bucket for different stack/env