This message was deleted.

No, self-managed backends such as S3 are still fully supported. This indicates a change in the layout mode to "project/stack" instead of just "stack". Its described here https://www.pulumi.com/blog/project-scoped-stacks-in-self-managed-backend

Thanks, that's a relief. What is the timeline for deprecation. as in: how much time do I have left for any refactoring of my stacks that may be necessary?

Engineering says the plan is to make it a soft error in 2-3 months and a hard error 2-3 months after that. I would recommend updating the state as described in that document sooner rather than later.

@billions-river-87988 a quick follow-up on this topic:

pulumi state upgrade

does not appear to work without interactivity. For example, running with

--non-interactive

yields the following in logs:

$ pulumi state upgrade --non-interactive --verbose 9
warning: Legacy non-project mode support for DIY backends are due to be deprecated this year. Please migrate to project mode by running 'pulumi state upgrade'. You can disable this warning by setting PULUMI_DIY_BACKEND_ACKNOWLEDGE_LEGACY_WARNING to true.
This will upgrade the current backend to the latest supported version.
Older versions of Pulumi will not be able to read the new format.
Are you sure you want to proceed?
Please confirm that this is what you'd like to do by typing `yes`: Upgrade cancelled

From this log, should I expect --non-interactive to work? On other commands, we can supply --yes, but this command does not support --yes argument to be passed through.

yes, that sounds like a bug

We purposefully execute all our automation through ci/cd, so it would be ideal. I'm sure we can workaround, but have tons of environments (branches). These stacks are often dynamically created based on conventions within the system

got it, makes sense. I will report this internally- do you have a pulumi org?

I do not believe so. We have our own s3 backend and run the cli through custom docker images. I can create an account though if that makes it easier for you to track?

ok, thank you

Thanks again for your help

Out of curiosity, since it sounds like you have a pretty robust setup- would your company be interested in hearing about some of our enterprise offerings- premium support and other features not available in open-source? Perfectly fine if you are happy with OSS (we are glad you are using it) just want to make sure you have what you need and are aware of some of our newer offerings.

Let me send you a direct message

I got a reply from the engineer- looks like that command was missing the

--yes

flag, so he went ahead and added it- https://github.com/pulumi/pulumi/pull/15648. If that PR gets merged it should be released shortly (as early as tomorrow)...

I appreciate your quick response, and the engineer's turn-around.

yeah me too 🙂

@billions-river-87988 It appears that was merged and prepared for a future release

v3.110.0

. Do you know what the deployment frequency of the docker images are? For example, use the pulumi/pulumi-dotnet docker image as a base image for our deployments.

Yes, thats the next release- they release at least weekly... he implied to me it might be today.

awesome; thanks!

good morning- Pulumi is now at 3.111.0, those changes should be available to try when you get a chance