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

<@U01PTHRNU2U> does this example help?
<https://github.com/jaxxstorm/pulumi-examples/tree/b63b5ccf4082677a57cf6fe1d20283fd62221e5c/typescript/aws/transit_gateway_multi_account>

<@UCWG26BH7> Sorry, I'm not seeing the waiting mechanism. I guess I should also mention that I'm not using the default route tables of the transit gateway.

I didn’t use the accepter, I used the resource share and attached it manually to get around this issue

if you want to stick with your path, you’ll need to set a dependsOn the `VpcAttachmentAccepter` and likely build the routes inside an `apply`

I suppose another wrinkle is that I'd like to keep the Pulumi projects scoped to a single AWS account if at all possible.

Back to the general problem, is there a way to have Pulumi "wait" for a condition to be true before proceeding? I'm not quite ready to convert all this to an Automation API program. Maybe something with a Command provider resource?

I can't seem to find anything along these lines in Terraform world either

&gt; Is there a way to have Pulumi “wait” for a condition to be true before proceeding?
it depends on the condition, you can do things inside an `apply` that poll something for example

:thinking_face: Interesting... any examples of that lying around, by chance?

<https://gist.github.com/lukehoban/fd0355ed5b82386bd89c0ffe2a3c916a>

<https://github.com/jaxxstorm/pulumi-examples/blob/2519023cd4f22acd564783f6f4445a44dd82df65/python/aws/wait-for-loadbalancer/__main__.py>