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

you can use `<http://ctx.Log.Info|ctx.Log.Info>("")` where `ctx` is the pulumi context

If your cloud provider isn't creating the endpoint (e.g., if AWS is creating an EC2 instance and you're starting nginx inside that), then you need more.
In a vanilla Pulumi program, you can't wait until a resource is finished post-creation "boot" or anything like that. Pulumi does the waiting, and it may choose to finish when the cloud provider says the resource is ready, rather than when you think the resource is ready (which may be a long time after).
To work around this, you need to call your Pulumi program from another program or script, and have that program/script do the waiting. There is automation-api which does this, but if you're checking a single HTTP endpoint, then automation-api is over the top. A single wait-curl-loop will do.