Make Support for making key vault cache population togglable

[alex-goncharov]

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 comments along the lines of "+1", "me too" or "any updates", 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.

Description

Commit f61338f introduced cache for key vaults, which gets a list of all key vaults in the subscription and then reads each for up to date details.

This poses a problem for subscriptions with a substantial amount of key vaults and a noticeable rate of changes, where one or two plans can lock down a subscription by hitting API rate limits.

Is it possible to make the cache feature togglable via provider configuration?

New or Affected Resource(s)/Data Source(s)

azurerm_key_vault

Potential Terraform Configuration

provider "azurerm" {
  features {
    key_vault {
     enable_cache = true|false
    }
  }
}

References

No response

[alex-goncharov]

With one of the subscriptions that look like this

$ az resource list --resource-type Microsoft.KeyVault/vaults --subscription XXX | jq '. | length'
894

An "application shell" in this subscription has a single KV in its resource group, and a couple of PRs lock the whole set-up down on version 3.106. 3.105 works fine.