Hello there, Just noticed that with Pulumi v3.31, and using our own FileBackend (Azure Storage account Container), after a destroy, there is a json.bak that is still persisted. Is this is a feature, or a bug? 😄

It's a feature, it was broken for a while but is fixed and working again now. https://github.com/pulumi/pulumi/issues/9474 was recently raised about this which as you can see was on v3.26.1.

So, is there a newer version of the CLI I need to download, or.... ?

No, there should be a .bak file left over that's the feature. A backup that gets automatically deleted isn't much help to anyone.

Hmm, okay. Is there a way to force delete the whole stack including backups? While we are testing, we indeed want to clear everything to reduce clutter, and having those baks, kinda is annoying...

^^ see https://github.com/pulumi/pulumi/issues/9474. We probably need to add a --include-backups flag to

stack rm

okay. Thank you @echoing-dinner-19531 Wasn't sure if there is already an option, or not. Btw, we are using the automation API which would also be changed with the feature, I guess.

yup, we try to keep automation api in sync with the cli. We've got some work planned to make sure of that.