No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Hi, between <http://github.com/pulumi/pulumi/sdk/v3|github.com/pulumi/pulumi/sdk/v3> v3.181.0 and <http://github.com/pulumi/pulumi/sdk/v3|github.com/pulumi/pulumi/sdk/v3> v3.182.0 "pulumi up" in interactive mode stopped asking:
Do you want to perform this update? [Use arrows to move, type to filter]
 yes
> no
 details

Is this a known issue?

<https://github.com/pulumi/pulumi/issues/20198>

Although I can't repro this, and the change pointed out on the ticket (<https://github.com/pulumi/pulumi/pull/19998>) doesn't change the prompt logic used for `up`.

Screenshot 2025-08-04 at 11.35.16.png

Screenshot 2025-08-04 at 11.33.21.png

Thank you Fraser. This is how I reproduced it.

Only thing I changed was the version of the SDK. The rest I analysed using AI, that can be completely wrong indeed. Is there any other way we could explain this behaviour?

Screenshot 2025-08-04 at 11.38.28.png

Related to this: pulumi up -f applies the changes. I would expect that I would need to add a --yes here for the changes to be applied

I have been fighting with this for a while, downgrading to v1.81 solves it for me. Not sure about the behaviour of the -f flag. I am using the go quickstart to reproduce this. Only thing I am sure of is, downgrading to v1.81 made it behave as expected for me.

Happy to share the firebase studio repo or do a call to show how I reproduce this.

oh interesting, its not so much skipping the confrimation but looks like its just erroring out without showing the error

Thanks for this, seen you've posted to github as well. We'll keep the thread over there, I think this might be related to shutdown logic that changed recenently