pulumi preview --expect-no-changes doesn't use different exit codes depending on the exit reason

[piotr-bzdyl-vertexinc]

Hello!

• Vote on this issue by adding a 👍 reaction
• To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details

Steps to reproduce

pulumi preview --expect-no-changes uses a single exit code for both cases

• there was an error while running preview of the changes e.g. due to network connectivity, issues with credentials etc.
• there are some changes to the resources detected

This makes it cumbersome to differentiate between these two situations and require workarounds.

It would be better to have an option similar to https://www.terraform.io/cli/commands/plan#detailed-exitcode.

$ pulumi version
v3.24.1

[dixler]

related to #3897

[rshade]

related to #5144

[BigDwarf]

Hello @dixler , do you mind assigning this one to me if it is still a case? :)

[dixler]

Hello @dixler , do you mind assigning this one to me if it is still a case? :)

Hey again. Thanks for the interest. I brought this up with the team and we're going to need to put together a more comprehensive plan around exit codes first. Will follow up.

[gunzy83]

Hey again. Thanks for the interest. I brought this up with the team and we're going to need to put together a more comprehensive plan around exit codes first. Will follow up.

@dixler Did a plan get created on this? I think a few of us would be keen to help make this happen but without knowing the internal plans at Pulumi this will be stalled indefinitely. We have had a number of deploys proceed and then error when the preview error should have been caught first.