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

We provision a “hub and spoke” network topology with several projects and stacks that span subscriptions. When provisioning spokes we use two providers to provision peering from hub to spoke and spoke to hub. When a spoke stack is destroyed peerings are properly removed, all good.  When the hub is updated all subnet peerings are dropped, not so good. Running Pulumi refresh and Pulumi up on each spoke stack restores the missing peerings but is there a better way? All spokes could be provisioned with a single stack but that feels wrong.  Thoughts?

I think these are both relevant to you: <https://github.com/pulumi/pulumi/issues/2209>
<https://github.com/pulumi/pulumi/issues/2309>

You could use Automation API and some work of your own to potentially make this easier for you in the meantime.

Otherwise using just CLI your solution:
&gt; Running Pulumi refresh and Pulumi up on each spoke stack restores the missing peerings
Is the current expected way to resolve this.

Thanks for the validation Joshua, 2309 sums it up.  I'm going down the road of orchestration to update dependencies now.