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

:wave: Looking for advices on how to best organize Pulumi projects. Out of all projects we have, one is `compute` and one is `observability`. Conceptually, `compute` is a dependency of `observability`. However, as part of `observability`, we build services that requires resources in the `compute` project, which take dependency on `observability`. So this results in a circular dependency.

How do you handle this as your projects grow? Any best practices that you can share? Thank you :bow: !

There are different views but this has a gr8 explanation of how to organize. It's a bit dated but I think answers your question. 
<https://www.pulumi.com/blog/iac-recommended-practices-structuring-pulumi-projects/|https://www.pulumi.com/blog/iac-recommended-practices-structuring-pulumi-projects/>

we were just chatting about this in a separate thread! :smile: check it out: <https://pulumi-community.slack.com/archives/CDE799L1M/p1721747071958529>

apologies; that thread was moreso around resources in a single project and you're asking about project -&gt; project.

agreed, the zephyr blog series is a good read. Stack references _can_ be circular but require a bit of additional care to get right. One solution is to have a 3rd project referenced by both.