https://pulumi.com logo
#general
Title
# general
m

millions-furniture-75402

09/14/2023, 7:15 PM
pulumi state upgrade
will make upgraded stacks inaccesible to older versions of Pulumi. This is a one-way operation. Once you have upgraded your backend, you cannot downgrade to the previous version.
https://www.pulumi.com/docs/concepts/state/#scoping Other than requiring Pulumi version 3.61.0+, what are the implications? Does this impact any features?
e

echoing-dinner-19531

09/14/2023, 7:54 PM
This allows you to use project scoped stacks, so you can have "my-project/dev" "my-other-project/dev", where the project name is picked up automatically from the Pulumi.yaml. Aligns with how names work with the service, and is a lot nicer than having to remember to prepend your project name to every stack name.
m

millions-furniture-75402

09/15/2023, 1:00 PM
Right, okay, I suppose that answers my question too, stack references could become problematic. Where we have overcome this limitation using our own namespace.
I'm also left a comment here in regards to a point of friction moving between state backends https://github.com/pulumi/pulumi/issues/12173#issuecomment-1721166693
e

echoing-dinner-19531

09/17/2023, 7:51 PM
Sorry, been offline for a few days but I've replied to that comment now.
m

millions-furniture-75402

09/18/2023, 1:01 PM
Thank you, that solution would ease migration between state backends 100%