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

Please open issues with repro steps and we'd be happy to work on improving error messages where they prove to be unhelpful!

To be fair, part of the problem I'm having is getting used to Python tracebacks again. I'm used to Scala where we don't throw exceptions for expected errors and instead return an error types. I guess it's the Python way to fail with an unhandled exception for cases where property values are missing or have incorrect values. It would be nice if there was at least a way hide all the unnecessary part of the traceback from the runtime.

I was having some fun errors yesterday which as far as I could tell from Googling were coming from a go library which had no context to the error what so ever. If I can remember what those were then I'll report it.

you can also do your preview / up with `--diff` to get more details that might help and there is `-v=&lt;int&gt;` and `--debug`