able-doctor-68496
07/16/2021, 12:37 AMinfrastructure
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?little-cartoon-10569
07/16/2021, 12:58 AMbackend: url:
property (they can be different keys in the same bucket), or discriminiate stacks with projects names.billowy-army-68599
infrastructure.dev
able-doctor-68496
07/16/2021, 6:14 AMprehistoric-nail-50687
07/16/2021, 9:17 AM