azurem_key_vault_key: Refreshing state with context deadline exceeded

[wuxu92]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Terraform Version

1.3.7

AzureRM Provider Version

2.92.0/3.74.0

Affected Resource(s)/Data Source(s)

azurerm_key_vault_key

Terraform Configuration Files

resource "azurerm_key_vault_key" "test" {
  name         = "key-442ot"
#  key_vault_id = data.azurerm_key_vault.test.id
    key_vault_id = "/subscriptions/xxx/resourceGroups/xuwu1-rg/providers/Microsoft.KeyVault/vaults/acctestkv-442ot"
  key_type     = "EC"
  key_size     = 2048

  key_opts = [
    "sign",
    "verify",
  ]
}

Debug Output/Panic Output

Error: retrieving the Resource ID the Key Vault at URL "
https://ue1-key-vault-06.vault.azure.net/":
listing resources matching "resourceType eq 'Microsoft.KeyVault/vaults' and name eq 'ue1-key-vault-06'": resources.Client#listNextResults: Failure sending next results request: StatusCode=0 -- Original Error: context deadline exceeded
│

Expected Behaviour

terraform apply success w/o error

Actual Behaviour

Error: retrieving the Resource ID the Key Vault at URL "
https://ue1-key-vault-06.vault.azure.net/":
listing resources matching "resourceType eq 'Microsoft.KeyVault/vaults' and name eq 'ue1-key-vault-06'": resources.Client#listNextResults: Failure sending next results request: StatusCode=0 -- Original Error: context deadline exceeded
│

Steps to Reproduce

No response

Important Factoids

No response

References

The old provider use a 5min read timeout value, this is too short if there are many resources under the subscription. And if the resource has already provisioned by terraform and the 5min timeout value has been written to the state file and the state refresh of next terraform apply won't use the custom timeout value but use 5min from state file.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.