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

The issue here is that the Azure API tells Pulumi that it's done before the deployment has taken place. You could set up polling to check when the resource has finished deploying?

Same thing happens with public IP address allocation. API says it's done even if the address is not available yet

This is an example of me handling this scenario with Kubernetes Ingress Controller:

```const ingressIpDone = pulumi.all({
    name: ingress.ingressLoadbalancerIP.name,
    resourceGroupName: cluster.nodeResourceGroupName
});

const ingressIP = ingressIpDone.apply(d =&gt; {
    return azure.network.getPublicIP({
        name: d.name,
        resourceGroupName: d.resourceGroupName
    }, { async: true }).then(ip =&gt; ip.ipAddress);
});```

Now I can just refer to `ingressIP` and it's an `Output` that gets realized after the IP address is available

So basically what it does is that it first waits for the Azure API to say that "yeah, IP created". This is the first part of the code. Then when this happens it explicitly queries Azure API for details regarding that resource

Azure does create the resource immediately after the API call has been made, it just doesn't mean it's ready for usage

<@U01FB0HRB2Q> sure I appreciate that Pulumi just reflects responses from api calls to Azure. Since starting this question I looked at the resource activity log that can be viewed via the Azure Portal for each resource. The activity log events seem to track the real resource creation progress events behind the api calls.

There is something called the Azure Resource Graph with an associated KQL query language. Maybe I could join across all resources in a resource-group the Azure resource activity log and the resources created in a stack.UpAsync() call.

<https://docs.microsoft.com/en-us/azure/governance/resource-graph/overview>

<@U0204V35NCT> as you say, on return from a Pulumi UP call the Azure resources are created and I can see them listed in the Azure Portal within seconds. "Ready for use" is a subsequent progress event in what I assume is a mini internal state-machine within Azure for each resource creation event.

Yeah. You just need to figure out how to find out when that specific resource is actually ready. It can be practically anything

If you want to connect a managed database (like postgre) you can try to use normal SQL libraries

If it is unreachable from where you are running Pulumi then you need to do something else

<@U0204V35NCT> I cannot find pulumi.All() in the .Net automation API, I assume you are using TypeScript or Go?

<@U025Z6MCEER> it is `Output.All` apparently

See <https://www.pulumi.com/docs/intro/concepts/inputs-outputs/#all>