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 <@U01E4107Y07> 

Pulumi won’t traverse the tree - if you want to run up against a vpc project then cd to that folder where the Pulumi.yaml file can live and it will stay in the confines of that package

Personally I’m more a fan of splitting out to smaller projects to reduce the chance of destroying things inadvertently 

So if you want to destroy only the eks cluster then you would do that and not the vpc

This post may help in that thought process <https://www.pulumi.com/blog/architect-aws-application-infra-with-pulumi-stack-references/|https://www.pulumi.com/blog/architect-aws-application-infra-with-pulumi-stack-references/>

Let me know if you have any other questions

The automation API gives you the ability to select which stacks to `up`, `preview`, etc. without weird config tricks, and also makes it a lot simpler to re-use code