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

That's exactly what we do, we have an internal error lib that wraps and enriches pulumi errors so we can more easily track them. There's also a verbosity flag you can add to the `up/preview`

the verbosity flag didn't seem to give me better error context, i.e stacktrace/line number/resource name

but thanks for the response.  What properties do you enrich your errors with specifically?