Update dependency Microsoft.Extensions.Configuration.AzureAppConfiguration to v8 #3493
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.2.0
->8.0.0
Release Notes
Azure/Azconfig-DotnetProvider (Microsoft.Extensions.Configuration.AzureAppConfiguration)
v8.0.0
Compare Source
8.0.0 - October 3rd, 2024
Breaking Changes
AzureAppConfigurationRefreshOptions.SetCacheExpiration
andFeatureFlagOptions.CacheExpirationInterval
have been deprecated and will be removed in a future release. They are replaced withAzureAppConfigurationRefreshOptions.SetRefreshInterval
andFeatureFlagOptions.SetRefreshInterval
, respectively. This change does not affect functionality but aims to eliminate confusion regarding cache expiration implied by the previous API names. #350Enhancements
Variant Feature Flags and Telemetry: This is the first stable release with support for the
variants
,allocation
, andtelemetry
properties for feature flags added by version 4.0.0 of the Microsoft.FeatureManagement.* libraries. While variant feature flags can still be toggled on or off, they also allow for different configurations, ranging from simple primitives to complex JSON objects. Variant feature flags are particularly useful for feature rollouts, configuration rollouts, and feature experimentation (also known as A/B testing).This is the first stable release of the load balancing mode introduced in 8.0.0-preview.3. Load balancing enables your application to distribute requests to App Configuration across all available replicas. This enhancement improves the scalability of applications that typically experience high request volumes to App Configuration, ensuring they remain within quota limits. Load balancing mode is off by default and can be activated by setting the new
AzureAppConfigurationOptions.LoadBalancingEnabled
property totrue
. #535Added the ability to configure options used to connect to Key Vault resources that have no registered
SecretClient
with the following new API. #274This API can be called from within the
AzureAppConfigurationOptions.ConfigureKeyVault
method.v7.3.0
Compare Source
Microsoft.Extensions.Configuration.AzureAppConfiguration 7.3.0 - July 16th, 2024
Enhancements
Azure.Security.KeyVault.Secrets
to4.6.0
. #572Bug Fixes
TryRefreshAsync
is invoked or when theoptional
argument is true in theAddAzureAppConfiguration
method. #551Microsoft.Azure.AppConfiguration.AspNetCore 7.3.0 - July 16th, 2024
Microsoft.Extensions.Configuration.AzureAppConfiguration
reference to7.3.0
. See the release notes for more information on the changes.Microsoft.Azure.AppConfiguration.Functions.Worker 7.3.0 - July 16th, 2024
Microsoft.Extensions.Configuration.AzureAppConfiguration
reference to7.3.0
. See the release notes for more information on the changes.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.