Closed mced closed 3 years ago
Do you still see this issue? Like we saw in #88, it sounds like the issue could be that our backend had problems: https://status.cloudamqp.com/incidents/v9n02mkw0zpk
If you get rate limited, the HTTP response will indicate that with status code 429
Yes, still...
@mced Okay, that's no good. Can you contact our support so we can take a closer look? https://www.cloudamqp.com/support.html (great if you refer to this issue and provide more details about your account)
Chaining the plugin resources with depends_on
is a solution to avoid this error.
Is it possible to change the provider default polling timeout setting ? At this moment this is not implemented and I believe this will solve this issue
@mced @crisp2u Sorry for the delay on this response. Main reason for the error talking to backend, is that our underlying API fails to get a response in time talking directly to the server hosting Rabbit MQ. To solve this we have introduced a multiple retry request in our Go API-wrapper (go-api). From our testing this made a huge difference. Available in
Then to enable multiple plugins at once, @mced solution is the current way to go. Add depends_on
to chain plugin resources to let one resource finish before the other. Limited by only one plugin can be enabled at once in Rabbit MQ and our underlying API. Added an example to our documentation in Terraform registry.
All this is now available in the current latest release for our provider v1.11.0.
Will close this issue for now. Please feel free to re-open this issue if it still is an issue.
I've non systematic errors with the following error message:
I suspect that I'm hitting the api rate limiting even I've only 8 plugins across 3 instances...
Do you have any suggestions to avoid these errors ?