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

bummer, was hoping to start using this. project is awesome though

Thanks for the info

<@UD2HJDBCL> I’m curious to hear what the problem is

is the issue just that you don’t want the state to be in the Pulumi service?

I dont want deployment to not work if the cloud service is down

everyone here is already using terraform with s3 remote state

dont wanna talk security into allowing yet another oauth github app

What do you mean by having S3 support “built in” then?

That issue tracks whether the statefile is stored in Pulumi or in the service’s database, right?

In general to provide locking _some_ service would have to be involved, right?

basically, if you go under. we still need to be able to work in a team env

Right, that should work with the local backend.

You can just make your CI/CD solutino that invokes `pulumi up` be the lock, right?

with the local backend, I have to git recomit and push

Why not just have your CI/CD scripts push/pull from s3?

Your CI/CD is going to “lock” anyway, right?

because we also need the ability to apply locally

if it was just ci system launching it I wouldnt care so much for locking

This is one place where terraform apply really works out.

we are using that heavily for gitops right now

but the architecture of TF is a pain point right now

Having a separate plan/apply makes this nice.

You mean, the statefile stuff, or something else?

that just baffles me. no bool toggles for resources that are modules

Yeah, making a new language is hard. :slightly_smiling_face:

right, I don’t want to sound like I dont appreciate the work all the people put into it.

No, I feel your pain. I used to work on a system like that.