I’m getting confused about everything regarding cloud state storage. I find the following issues and/or PRs: • Backend setting in project config (https://github.com/pulumi/pulumi/pull/2813) • Persist filestate backend URL in Pulumi.<stackname>.yml (https://github.com/pulumi/pulumi/issues/2996) • Project name in stack identity inconsistent between backends (https://github.com/pulumi/pulumi/issues/2522) • Using S3 backend with multiple projects is unpleasant (https://github.com/pulumi/pulumi/issues/2814) This is a bit of a mess. The first two issues seem to contradict: is a backend URL project or stack specific? Also, if each project can have a different backend, how can project B which has a StackReference to A find the state backend of A? On top of that, how can Pulumi be logged in into different backends?

I agree it’s far from great. FWIW, there is a plan to clean this up before 2.0 (in Q1).

To add one more issue on that pile, I dislike

login

being user-level global: https://github.com/pulumi/pulumi/issues/3747

Totally agreed on feedback here @limited-rainbow-51650. As @tall-librarian-49374 notes this is something we’re planning on doing significant work on this quarter. Many of the issues are related to just two structural underlying details of the current implementation.

Thanks for the notice @white-balloon-205. I was able to convince another of our customers to go the Pulumi way, but the cloud storage backends are currently biting me back. And convenience of working on a single laptop for multiple customers is what I need in the new issue I created. Nevertheless, I very much like Pulumi. 😄

We had hoped to tackle this full space on the path to

2.0

, but had to scope it out of

2.0

due to a lot of other areas of focus. It will be a high-priority area to tackle holistically immediately after the

2.0

release. We unfortunately don't yet have a complete cross-cutting plan here - except that we know we need to broadly overhaul the user-facing backend model to deeply address the class of issues here. I will try to write up what I currently expect we'll need to do here in a single issue to try to unify some of the discussions - but I'll admit that I don't have a full vetted plan yet.