I’m working with Pulumi and the S3 backend. I have two Pulumi projects -

infrastructure

and

application

. The

infrastructure

project has a single stack:

internal

. The

application

project has a single stack:

dev-aws

. When I do

pulumi stack ls

in either project, I see both stacks:

$ pulumi stack ls
NAME       LAST UPDATE  RESOURCE COUNT
dev-aws    n/a          n/a
internal*  n/a          n/a

That is not what I expect. I can also select (e.g.) the

dev-aws

stack when I’m in the

infrastructure

project. This is clearly a mistake, but it will create a new

dev-aws

stack within the

infrastructure

project when I run

pulumi up

from the

infrastructure

project with the

dev-aws

stack selected. Why is it doing that? Is there some other recommended way to manage multiple projects with the S3 backend?

You have two choices: you can specify different S3 backends via the

backend: url:

property (they can be different keys in the same bucket), or discriminiate stacks with projects names.

what tenwit said ^^

Ok, thanks for the explanation. I definitely want to access the infrastructure outputs in the application stacks, so I guess I’ll need to use the naming conventions suggestion.