Handle 429 errors from Logz.io API

[smelchior]

We have a terraform state that defines multiple subaccounts:

resource "logzio_subaccount" "test1" {
...
}
resource "logzio_subaccount" "test2" {
...
}
resource "logzio_subaccount" "test3" {
...
}

(in total 9 accounts). When applying this state we get 2-3 429 errors:

│ Error: API call GetSubAccount failed with status code 429, data: Too Many Requests
│
│   with logzio_subaccount.test1,
│   on main.tf line 6, in resource "logzio_subaccount" "test1":
│    6: resource "logzio_subaccount" "test1" {
│
╵
╷
│ Error: API call GetSubAccount failed with status code 429, data: Too Many Requests
│
│   with logzio_subaccount.test2,
│   on main.tf line 21, in resource "logzio_subaccount" "test2":
│   21: resource "logzio_subaccount" "test2" {
│
╵
╷
│ Error: API call GetSubAccount failed with status code 429, data: Too Many Requests
│
│   with logzio_subaccount.test3,
│   on main.tf line 120, in resource "logzio_subaccount" "test3":
│  120: resource "logzio_subaccount" "test3" {
│

This should be handled inside the module with some kind of exponential backoff. We currently cannot apply this state properly.

[mirii1994]

Thanks for letting us know. We will add a backoff in our next version.

[mirii1994]

@smelchior v1.8.2 is out and should handle this. Can you please confirm that your issue was resolved? :)

[smelchior]

@mirii1994 works perfectly, thanks for the quick fix!