This message was deleted.

so in the AWS provider there is a resource called an ACM Certificate . When you create this resource, pulumi returns after the resource is deployed but before the certificate is validated. So if you are deploying another resource that depends on the certificate being validated you must also declare a ACM Certificate Validation. The Certificate Validation resource does not actually deploy anything, but rather it just represents the asynchronous action of validating the certificate. That way other downstream resources can get the

Output<T>

from the Certificate Validation when they rely on a validated cert - and Pulumi doesn't consider the Certificate Validation "deployed" until the validation is complete. Perhaps you need something similar since your function resource is returning after the function is deployed but before the function is ready. Then resources that rely on the function being ready could instead depend on this theoretical

FunctionReady

resource. Maybe you could checkout those implementations and see if that helps you come up with a solution?

Hi Joshua, thank you for the answer! Seems, that this is a common problem with other resources, too. Since there are already some implementations, there might be a similar implementation for Azure Resources. I need to take a close look at the whole Api, may be I have overlooked something. But thanks for sharing your solution!