This message was deleted.

sparse-intern-71089

03/10/2021, 1:28 AM

This message was deleted.

little-cartoon-10569

03/10/2021, 1:30 AM

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

shy-oxygen-8874

03/10/2021, 1:31 AM

It said it had been created

shy-oxygen-8874

03/10/2021, 1:32 AM

Copy code

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

little-cartoon-10569

03/10/2021, 1:33 AM

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

little-cartoon-10569

03/10/2021, 1:34 AM

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.

shy-oxygen-8874

03/10/2021, 1:35 AM

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

little-cartoon-10569

03/10/2021, 1:35 AM

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..

shy-oxygen-8874

03/10/2021, 1:36 AM

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

shy-oxygen-8874

03/10/2021, 1:37 AM

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

sparse-park-68967

03/10/2021, 1:59 AM

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

Open in Slack

Previous Next

Pulumi Community

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.