Hello, is there a way to slow down pulumi polling...
# azure
p
Hello, is there a way to slow down pulumi polling for resource creation state? I know of the --parallel argument, but I only want to slow down the read operations as we've been seeing lots of 429s on reads from the Azure lately (FYI we aren't aware of any reason for increased traffic - I'm suspecting either a change in the Azure rate limits, or in the Pulumi). Thanks
👀 1
b
I don't know of anything right off-hand, but I'll ask around and see if there is anything like that.
Do you have the request/response headers for those 429s?
p
Hi, yes, here is a sample: Response status: 429 Response headers: 'Cache-Control': 'no-cache' 'Pragma': 'no-cache' 'Content-Length': '341' 'Content-Type': 'application/json; charset=utf-8' 'Expires': '-1' 'Retry-After': '10' 'x-ms-failure-cause': 'gateway' 'x-ms-request-id': 'f0e56d1e-8735-4d12-9c59-94d591376712' 'x-ms-correlation-request-id': 'f0e56d1e-8735-4d12-9c59-94d591376712' 'x-ms-routing-request-id': 'UKSOUTH20250902T165315Zf0e56d1e-8735-4d12-9c59-94d591376712' 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains' 'X-Content-Type-Options': 'nosniff' 'X-Cache': 'CONFIG_NOCACHE' 'X-MSEdge-Ref': 'Ref A: 9BBAE23DD9354D8EAB9EB323B4FF824C Ref B: AMS231032609011 Ref C: 2025-09-02T165315Z' 'Date': 'Tue, 02 Sep 2025 165315 GMT' Response content: {"error":{"code":"SubscriptionRequestsThrottled","message":"Number of 'read' requests for subscription '<GUID>' actor '<GUID>' exceeded. Please try again after '10' seconds after additional tokens are available. Refer to https://aka.ms/arm-throttling for additional information."}}
FYI I also have an open ticket on this with the MS Azure Support, bud I already know they wont increase these hard limits. And also, there is this issue, which unfortunately does not seem to be progressing: https://github.com/pulumi/pulumi-azure-native/issues/3720 With that, you have all the information I do. Obviously it would be ideally solved by retrying the 429s with after the number of seconds specified in the "Run-After" header, but at this point, any workaround that does not severely slow down the pulumi up / refresh / preview would be great. Thank you very much for looking into it!