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

Is it correct that pulumi is storing a stack trace in state referencing files from my environment unrelated to the actual project source code?
<https://gist.github.com/antdking/3a8a6cef67270a7b8d9379c9f7d2fb63|https://gist.github.com/antdking/3a8a6cef67270a7b8d9379c9f7d2fb63>

Seems excessive, and will cause a lot of churn when working with multiple people

We do. We've been doing this for quite a while now (I want to say since 2023?) - in all our customers, I can't say that it's caused any issues with state changes and we have some very large customers with very large state files and very large numbers of employees all updating.

We have concurrency built in so that would solve a lot of those kinds of problems

I knew about the main source location for tracing resource definitions. It's that the stack trace has reference to the stack outside of the project code's scope seems odd

For example, lines 33-35 in your gist link above?

That is a good point - let me ask internally