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

Hi community!
Is there a tool in the Pulumi ecosystem similar to Terragrunt that helps coordinate multiple Pulumi projects—for example, handling init, destroy, and managing dependencies between them?
Would the Pulumi Automation API be the right comparison here?

If you always run all your projects together, then yes, automation-api is suitable and worth investigating. If you run all your projects together sometimes (e.g. when creating a brand-new environment) but often don't want to run them together (e.g. "redeploy the app but leave the network and database alone"), then automation-api might be more than you need: a simple deployeverything.sh would be fine.

You can craft an automation-api solution that orchestrates standalone (non-inline) projects for that middle-ground option. Alternatively, chained CD (or even CI) pipelines can do the same job, and I find that many developers find that solution easier to reverse engineer (which is good when dealing with tech transfers, which I often do when developing for a client then handing the solution over).

thank you paul, that makes sense
i'll stick with our CI for the moment then, dependency between projects is simple atm