Releases: Azure/AppConfiguration-JavaScriptProvider
Releases · Azure/AppConfiguration-JavaScriptProvider
1.1.2
1.1.0
1.0.1
1.0.0
1.0.0-preview.4
Update version to 1.0.0-preview.4 (#58)
1.0.0-preview.3
Enhancements
- 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
1.0.0-preview.2
Breaking Changes
- Changed the behavior when multiple labels are filtered in one selector. In the JavaScript provider configuration settings are loaded into a
Map
containingkey
andvalue
, without preserving thelabel
. If multiple labels are matched in one selector, the provider cannot determine which one to use. Now it will throw an error if label filter contains*
or,
. #22
Enhancements
- Added more information to the doc comments for better IntelliSense. #32
Bug Fixes
- Fixed wrong precedence of selectors after deduplication. #31
- Fixed type mismatch for
ConfigurationSettingId.label
by updating @azure/app-configuration to 1.5.0. Azure/azure-sdk-for-js#27607 - Fixed retry logic when host of configuration store cannot be resolved, by updating @azure/core-rest-pipeline to 1.12.2. Azure/azure-sdk-for-js#27037
Full Changelog: 1.0.0-preview.1...1.0.0-preview.2
1.0.0-preview.1
Fixed
- Updated version of @azure/identity to 3.3.2, for CVE-2023-36415
1.0.0-preview
Added
- Basic features for loading settings from configuration stores. #1
- Support authentication with connection string or AAD.
- Select settings with key/label filters.
- Trim key with prefixes.
- Support to resolve Azure Key Vault secret references automatically. #2
- Support to parse JSON objects for applicable content types automatically. #8