With the introduction of time-based retries on startup, the provider now continues attempting to connect to Azure App Configuration to load the initial configuration until the startup timeout elapses, or until the connection is successful.
Currently, Key Vault secret reference resolution in the provider does not respect the configured startup timeout allowance. If Key Vault is momentarily down during startup and secret references are used in the configuration then startup will fail if the default Key Vault retry count (3) is exceeded. This will surface as a KeyVaultReferenceException.
The provider should be updated to recognize transient Key Vault errors, such as momentary unavailability and retry as long as the startup timeout allows.
With the introduction of time-based retries on startup, the provider now continues attempting to connect to Azure App Configuration to load the initial configuration until the startup timeout elapses, or until the connection is successful.
Currently, Key Vault secret reference resolution in the provider does not respect the configured startup timeout allowance. If Key Vault is momentarily down during startup and secret references are used in the configuration then startup will fail if the default Key Vault retry count (3) is exceeded. This will surface as a
KeyVaultReferenceException.The provider should be updated to recognize transient Key Vault errors, such as momentary unavailability and retry as long as the startup timeout allows.