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

&gt; If I make a code change to that component resource and push it up to git, how do I ensure that all 20 website stacks are updated?
If you're using a local ComponentResource (ie: a local import) it would just work. If you've created a package component, you'd need to update your deps for your language (ie your package.json)

&gt; And if those stacks have outputs that other stacks use, say each website has a DNS module that depends on it to point some domain to the site, how would I ensure that those downstream stacks are all updated?
If you have a downstream stack that has changed, you'll need to run an `up` on that stack first to update the outputs. You can either:
• run your `pulumi up` sequentially in your pipeline for a nice easy win (bearing in mind if there are no changes, the run won't make any changes
• use the automation API to create a wrapper program/script that does the logic for you

&gt; run your `pulumi up` sequentially in your pipeline
Just to confirm, that means that this would be a manual process running that command in each directory individually?

unless you use Automation API, yeah. You can do `pulumi up -C &lt;dir&gt;`

Got it, I'll look into the Automation API then. Thanks!