This message was deleted.

maybe because the .pulumi is only dedicated to only one project ?

Thanks for the response but I'm not sure what you are suggesting as a solution? In the first scenario I had a single .pulumi folder but was then getting name conflicts between stacks in different projects (i.e. project1 and project2 couldn't both have a stack called dev). In the second scenario I had subfolders for each project each containing a dedicated .pulumi folder. This avoided the stack name conflicts but I then had to log in separately to each project and I also couldn't work out how to reference one project from the other using stackReference. Can you explain either how to use stackReference with the second scenario or better yet how to avoid the name conflicts in the first scenario so I only have a single login to deal with rather than a login per project? It would be nice to end up with a structure like that below but I'm not sure how to achieve it? .pulumi project1 stacks project2 stacks

This is ultimately due to https://github.com/pulumi/pulumi/issues/2522 and https://github.com/pulumi/pulumi/issues/2814, both of which we’d like to see get fixed in the filestate backends. Today - you can only use StackReference within a single backend. And to avoid name conflicts, until 2522 is addressed, most users are generally using

<project>-<stack>

naming convention for their stacks - such as

webapp-prod

.

Thanks Luke. Looks like this issue have been recognised for some time then (and recently pulled from the 2.0 release). Hopefully it gets looked at soon.