wooden-queen-36575
06/02/2023, 3:14 PMpulumi stack select dev --create
is creating a legacy stack, though my pulumi version is v3.69.0
and I am deleting my ~/.pulumi
folder between runs. Is there a way to force always using the multi-project backend and never use the legacy style?echoing-dinner-19531
06/02/2023, 7:16 PMpulumi state upgrade
command.wooden-queen-36575
06/02/2023, 9:18 PM~/.pulumi
folder yet, so it's using the legacy style on initial creation of that directory when I run pulumi stack init dev --create
. Also, when I run this in a fresh CI/CD environment, it seems to successfully instantiate with the new state style when I run pulumi login --local
but if I run pulumi login <file://some-other-path>
it creates some-other-path/.pulumi/stacks
in the legacy style.PULUMI_HOME
which had an additional configuration file in it, and I think that's what was causing the old style state. The confusion was that though I had PULUMI_HOME
set, pulumi login --local
stores things in ~/.pulumi
.echoing-dinner-19531
06/03/2023, 8:20 AMwooden-queen-36575
06/03/2023, 4:29 PMyarn install
adds plugins to the .pulumi
folder, which is enough to trigger the old state style. I'm able to work around this in my CI environment.