This message was deleted.

sparse-intern-71089

07/10/2023, 10:11 PM

This message was deleted.

ancient-policeman-24615

07/11/2023, 1:44 PM

Hey Danno, I’m not 100% sure I understand. Could you give an example? I’m not aware of any plans to allow observing provider behavior beyond the output of

pulumi up

with logs. We’re happy to take suggestions.

strong-helmet-83704

07/11/2023, 5:10 PM

I was provisioning a nat gateway and my eip limit was reached - it took a long time to error out…

ancient-policeman-24615

07/12/2023, 7:42 AM

Thanks for clarifying. It sounds like that kind of observability would require reaching into a provider to see what it is doing. You could experiment with running

pulumi

with higher log levels enabled. That will get you more insight into the provider’s operations.

👀 1

strong-helmet-83704

07/12/2023, 5:29 PM

thx. I remember there was an experimental pulumi observation feature - which would attempt to tail events from cloudtrail… i’m not sure it ever worked fully tho

strong-helmet-83704

07/12/2023, 9:32 PM

If i had to take an architectural guess… i’d say that Pulumi monitors the resource which it’s currently provisioning for status… but if this resource has an upstream resource dependency (like natgw depends on an eip) then the error returned from eip is not necessarily propagated back to the natgw api directly… which means we have to wait for the provisioning timeout… @billowy-army-68599 does this sound plausible?

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.