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

You could do a `sys.exit(1)` after the log.error.

To make it cleaner, wrap it in a function:

```def fatal(msg: str, resource: pulumi.Resource = None):
  log.error(msg, resource=resource)
  sys.exit(1)```

You could also pass in the exception to the function and throw it after the log:
```msg = str(exc)
log.error(msg)
throw exc
```
Though I'm not sure how that will look visually

The problem with sys.exit() is that it's not clean

And answering your last question, it would look something like:
```error: This is my custom error, it's all gone downhill
error: Program failed with an unhandled exception:
...```

It means I've confused it with `os._exit()` :sweat_smile:

I read through the launcher script, it looks like you'll get a cleaner error by using `pulumi.RunError` as the base of your exceptions:
<https://www.pulumi.com/docs/reference/pkg/python/pulumi/#pulumi.RunError|https://www.pulumi.com/docs/reference/pkg/python/pulumi/#pulumi.RunError>

With `pulumi.RunError` you essentially get what I want, which is a pretty error message followed by a clean exit, without a stack trace. :+1: