Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

keyvault: populating the cache using both the Key Vault List and Resources API to workaround incomplete/stale data being returned #26070

Merged
merged 3 commits into from
May 27, 2024

Commits on May 23, 2024

  1. keyvault: populating the cache using both the List Key Vaults endpoin…

    …t and the Resources Endpoint
    
    This commit:
    
    1. Registers a client for Resources@2015-11-01 and KeyVault@2023-07-01
    2. Updates the caching to retrieve the list of Key Vaults using both the List API for the ResourceType and using the
       Resources API directly - meaning we have a more up-to-date set of data.
    
    Notably we're using the older Resources API that the Azure CLI uses, more details can be found in hashicorp/pandora#4148
    however by loading both we're hoping to alleviate the caching issues we've seen.
    tombuildsstuff committed May 23, 2024
    Configuration menu
    Copy the full SHA
    f61338f View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    6561f56 View commit details
    Browse the repository at this point in the history
  3. imports

    tombuildsstuff committed May 23, 2024
    Configuration menu
    Copy the full SHA
    e883f62 View commit details
    Browse the repository at this point in the history