I'm trying to understand exactly how this change has effected my service managed stacks. Previously when I made a stack with

org/project/stack

, I could run

pulumi stack ls

and see all my stacks listed with

org/project/stack1

,

org/project/stack2

, etc. Additionally in the dashboard the stacks would all be grouped based on the project they were in. Now when I create a stack in an existing project with

org/project/stack

the

project

portion seems to be completely ignored. Running

pulumi stack ls

only shows

org/stack

, my starship module that reports the stack in my terminal prompt only shows

org/stack

, and the dashboard no longer groups the stacks by project. The only place I can actually see the project name is in the URL in the dashboard. This seems like the opposite of what this blog post is saying. Am I missing something or are projects just ignored now? (I understand that

org/stack

is a valid reference when in a directory for

project

, but that doesn't explain the dashboard portion.)

it sounds like you're not using the self-managed backend so the feature introduced in this update shouldn't apply to you possibly you are experiencing some bug?

That's the only thing I've been able to come up with.

Projects aren't ignored, they are implicit, this has been the behavior for as long as I remember with the Pulumi Service. The

Pulumi.yaml

contains the project, so specifying it is redundant. That being said, we ALWAYS use the fully qualified stack name to avoid any confusion.

it all changed from how it was working for us last week ¯\_(ツ)_/¯