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

after enabling / disabling modules, I did found which one was causing the issue… is it possible to give much better stacktrace, what exactly did run program?

Usually you would only see this error if you are running a pulumi program (ie one that makes SDK calls like `new aws.s3.Bucket(...)`) either without the CLI, or without calling `stack.up` in automation api.