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

Did the up say it had been created, or did it entirely "miss" that it needed to be created?

```+  aws:elasticloadbalancingv2:ListenerRule prod-web-listener-rule created```

ListenerRules aren't heavyweight.. it should create it immediately... odd.

As to your question: no, other than increasing the log level (e.g. `-v=9`) I don't think there's a way to be "more aware" of provisioning failures.

It's troubling--if the resource isn't there I'd expect to get a failure.

Yep. There are some sorts of resources where I accept that the request to create can be successful, and the actual creation might take a while and later be unsuccessful.. that's just clouds for you..

Yeah, I suppose, to a point. Although, the way CF handles that is to have a long poller for status

If you're counting on your deployment status for CI/CD, you'd hope there'd be a stronger guarentee

Could you cut a ticket with the details? As close a representation of your code as is possible would be great.