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

Hmm, any way for me to *reliably* wait for `azure.network.PublicIPAddress` to populate in such a way that it will *always* have the IP address available under `ipAddress` property? It's type signature in TS is `Output&lt;string | undefined&gt;` which I'm assuming is due to the fact that this output won't wait until it has got the IP address?

I'm now trying to circumvent this by waiting for a later resource "just in case" but this is kinda ugly and forces me to do stuff like
```ingressLoadbalancerIP.ipAddress.apply(addr =&gt; addr || 'NOT_AVAILABLE_YET')```

Here is one trick: <https://github.com/pulumi/examples/blob/258d3bad0a00020704743e37911c51be63c06bb4/classic-azure-ts-vm-provisioners/index.ts#L128-L135>

That is indeed much better even if that too is a bit wonky