This message was deleted.

That's not an error, just a warning. Might be the other user has set the envvar to turn it off. If you look inside the .pulumi folder you should find a "stacks" folder and in there is probably a plain json file from an old stack (i.e. not underneath a project folder)

ah, there were indeed some older stack files lying around. didnt notice those. thanks!

Partially. New versions of pulumi support "project based" file store, and will default to using that mode when creating a new backend location and can upgrade old backend locations to that mode with

pulumi upgrade

You can turn off that default upgrade with

PULUMI_SELF_MANAGED_STATE_LEGACY_LAYOUT=true

but any existing backend already in project mode will stay in project mode. Old versions of pulumi won't understand project mode, some more recent ones understand it well enough to error that it's unrecognized but very old versions will just write old style non-project scoped files to the backend.

Thats good to know! any details on whats whats “old” and “recent”? Maybe a blog post explaining that change? 🙂 are we good when everyone is using 3.63.0 and higher?

https://www.pulumi.com/blog/project-scoped-stacks-in-self-managed-backend/ 3.63 and higher should be fine

perfect, thank you!