[Bug]: No retry logic?

[Aransh]

Terraform Version

Terraform v1.9.2 on darwin_arm64

Linode Provider Version

version = "2.23.1"

Effected Terraform Resources

linode_object_storage_key

Terraform Config Files

No response

Debug Output

No response

Panic Output

No response

Expected Behavior

linode_object_storage_key (and other resources too probably) should have a retry mechanism in place, especially for server side errors

Actual Behavior

I constantly get 502 errors from Linode provider, a few restarts usually resolve it, but this should be handled on the provider side...

[2024-07-29T08:04:53.186Z] │ Error: Failed to create Object Storage Key
[2024-07-29T08:04:53.186Z] │
[2024-07-29T08:04:53.186Z] │ with module.a1-ddc-ato-heuristic.linode_object_storage_key.this[0],
[2024-07-29T08:04:53.186Z] │ on .terraform/modules/a1-ddc-ato-heuristic/linode-object-storage-key/main.tf line 17, in resource "linode_object_storage_key" "this":
[2024-07-29T08:04:53.186Z] │ 17: resource "linode_object_storage_key" "this" {
[2024-07-29T08:04:53.186Z] │
[2024-07-29T08:04:53.186Z] │ [502] Bad gateway
[2024-07-29T08:04:53.186Z] ╵
[2024-07-29T08:04:53.186Z] ╷
[2024-07-29T08:04:53.186Z] │ Error: Failed to create Object Storage Key
[2024-07-29T08:04:53.186Z] │
[2024-07-29T08:04:53.186Z] │ with module.yondu-unified-feed.linode_object_storage_key.this[0],
[2024-07-29T08:04:53.186Z] │ on .terraform/modules/yondu-unified-feed/linode-object-storage-key/main.tf line 17, in resource "linode_object_storage_key" "this":
[2024-07-29T08:04:53.187Z] │ 17: resource "linode_object_storage_key" "this" {
[2024-07-29T08:04:53.187Z] │
[2024-07-29T08:04:53.187Z] │ [502] Bad gateway

Steps to Reproduce

I guess manages a lot of linode access keys on Linode (us-iad-1 region in my case)... kind of a hard one to replicate, but a retry mechanism for this should be good for everyone either way

[zliang-akamai]

Hi @Aransh, thanks for the feedback!
We are currently looking to this and tracking it internally. We will let you know if we have any update.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[Aransh]

Not stale

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[Aransh]

Not stale

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[Aransh]

Not stale, still often fails without retry