This message was deleted.

sparse-intern-71089

02/19/2021, 9:52 AM

This message was deleted.

gifted-student-18589

02/19/2021, 9:56 AM

Right now, for local dev, the devs are storing state locally, and deploying from their own machine, with their own AWS account, for dev and testing needs. But in the CI/CD, we need a more persistent way of storing state, for our dev, staging, and production environments. So obviously,

file://

as a backend won’t do well there. 🙂

brave-planet-10645

02/19/2021, 10:06 AM

I guess if you're not sharing any of the infrastructure then you could use the local backend, but I would recommend using the Pulumi backend (which gives you extra features like access control and state locking) and if you really don't want to, then something like S3. Otherwise all your engineers are going to be working on their own version of the state

gifted-student-18589

02/19/2021, 10:12 AM

Thank you for the response @brave-planet-10645

👍 1

gifted-student-18589

02/19/2021, 10:16 AM

I’m aware of Pulumi as an ultimate backend, just wanted to do additional exploration. Regarding S3 buckets… we were thinking about simply putting the

s3://…

in our

Pulumi.yaml

project file (this file is checked into our git repo) and avoid the

file://

all together, but the thing is, every dev has its own AWS account, and only the account that created the S3 bucket would actually have access to it, and store state files via Pulumi. Additionally, the devs would have to create their own bucket, with a different name (since S3 buckets must be unique in name), and then we end up with another problem, where every dev would have their own Pulumi.yaml file, with their own backend set in it.

gifted-student-18589

02/19/2021, 10:17 AM

I guess this is one of the problems that Pulumi backend addresses, among others of course

brave-planet-10645

02/19/2021, 10:53 AM

You could create a central account that has an S3 bucket that they all have access to?

🤔 1

gifted-student-18589

02/19/2021, 11:11 AM

thanks, will take that into consideration too

Open in Slack

Previous Next

Pulumi Community

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.