Source code | Package (npm) | Samples
- Fixed a bug that could trigger concurrent data refresh. #136
-
Added support for automatic replica discovery for geo-replication enabled App Configuration stores, enhancing resiliency and scalability for non-browser-based applications. The feature is not available for browser-based applications due to the restriction of browser security sandbox. #98
-
Added support for load balancing mode which 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 disabled by default and can be activated by setting the new
AzureAppConfigurationOptions.loadBalancingEnabledproperty to true. #135 -
Added support for monitoring all selected key-values. Configuration will be refreshed if any of key-values are updated. Watching the sentinel key for refresh helps ensure data integrity of configuration changes, but it is now optional. This behavior is activated when you enable the refresh but do not specify any watched keys in
AzureAppConfigurationOptions.refreshOptions. #133
- Added support for injecting additional telemetry metadata
FeatureFlagId,FeatureFlagReference,ETagandAllocationIdto feature flags if telemetry is enabled. #101, #111
- Fixed a bug that caused
ReferenceErrorof optional chaining whenprocessis undefined. #104
- Added support for loading feature flags from Azure App Configuration. #65
- Fixed a bug that caused the error ‘ReferenceError: WorkerNavigator is not defined’ when running the application in a browser. #81
This is the first stable release of the following features.
- Loading and composing configuration with key-value selectors.
- Authentication with connection string or Microsoft Entra Id.
- Loading key-values as either a
Mapor a configuration object. - Trimming prefixes from keys.
- Loading key-values with JSON content type as configuration objects.
- Key Vault reference resolution.
- Support for dynamic configuration refresh.
Get started with the quickstart.
- Excluded feature flags from loaded settings. For example, if you attempt to load all settings by specifying a selector with
keyFilter: "*", only configuration settings are included now, whereas previously feature flags were also loaded. #55
-
Added support for dynamic configuration refresh. See an example here. #21
-
Added support for consuming configuration as an object. A new API,
constructConfigurationObject, has been added to construct a configuration object based on the key-values loaded from Azure App Configuration. It minimizes necessary code changes for applications that were using JSON configuration file to adopt Azure App Configuration. #49
- The label filter in a selector is restricted to a single label. An error will be thrown if a label filter contains
*or,. This change is to avoid the ambiguity when multiple values are loaded for the same key. Key-values with different labels can still be loaded using separate selectors for proper configuration composition. #22 - Fixed a bug where the last selector may not take precedence if multiple selectors with the same key and label filters are provided. After applying the fix, the resulting configuration of an application may change. To ensure the intended configuration composition, remove any duplicated selectors.#23
- Updated the reference of
@azure/core-rest-pipelineto1.12.2, which added retry for DNS resolution of App Configuration endpoints. Azure/azure-sdk-for-js#27037
- Updated the reference of
@azure/identityto3.3.2, addressing CVE-2023-36415
Added support for
- authentication with connection string or Microsoft Entra
- loading and composing configuration with key-value selectors
- key prefix trimming
- Key Vault reference resolution
- Key-value with JSON content-type