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

What’s the problem with the code as it is? Pulumi should be waiting for the sa to be created because you are referencing it in `pulumi.all`.

Hey <@UGDSK5RNC> thanks for the quick reply. I pressed enter too soon - edited the post now. So `pulumi.all` is the callback I am looking for then?

With your edit I can see what you are looking for, and I think there is a very hacky way to do it, but nothing native if I recall.

I think <https://github.com/pulumi/examples/tree/master/aws-ts-ec2-provisioners> may be what you are looking for, but someone else may have a much better answer.

With automation api you can subscribe to engine events and check for actions against specific resources and take action.

If you just want to do it in your Pulumi program, you can do in your code within an apply on an output from the storage account (which tells it to wait for the SA to be finished) and you’ll want to check for IsDryRun on the current deployment so that you aren’t taking your action during Pulumi preview

Hey <@U01E602D5JA>, that is exactly the problem I was currently facing. Also when you use `pulumi up` locally you have the option to cancel the update. The `apply` function executes regardless. Can you elaborate on checking for IsDryRun on the current deployment? Where is that value value be listened to?

I'm assuming you're using typescript? This is the `IsDryRun` function: <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/runtime/#isDryRun>

It's in the `pulumi.runtime` module

ah gotcha, so I can just use `pulumi.runtime.isDryRun()` to decide

thanks a lot Joshua! I appreciate the help