As part of fixing the exit bug recently, we accidentally made errors lead to zero exit codes. As a result, the Pulumi CLI thought the prgoram exited ordinarily, and proceeded to do its usual planning and deployment, rather than terminating abruptly. This is a byproduct of how Node's process.uncaughtException handler works. It hijacks and replaces all usual error logic, including the process.exit part. This change simply adds back the non-zero exit. I also added a test (and fixed one other that began failing afterwards), so that we can prevent regressions down the road. |
||
---|---|---|
.. | ||
dynamic-provider | ||
langhost | ||
run |