The Azure App Configuration extension in Azure DevOps pipeline has been published to Azure DevOps marketplace. The version of the Azure App Configuration task being used will print to the console when the task is executed:
- Added support for Node.js 20. This pipeline task now supports both Node.js 16 and Node.js 20.
Breaking changes
- Updated to fail the task if any Key Vault references cannot be resolved or if the resolved values are unable to be set as a pipeline secret. To avoid failing the task due to Key Vault errors, you can enable the new option to treat these errors as warnings detailed below.
Enhancement
- Added an option to treat Key Vault resolution errors as warnings.
- Added capability to use workload identity federation for authentication.
Breaking changes
- Updated the task to require Node.js 16. It previously required 10.
- Updated the minimum supported azure pipeline agent version to 2.206.1 or later. Previously it was 2.144.0.
Bug fixes
- Fixed a bug that caused an invalid secret URL warning when resolving key vault references in sovereign clouds.
Fixed a bug that caused an invalid_client error when using certificate-based authentication #608.
-
Breaking change: With the added support of sovereign clouds such as Azure Government and Azure China, the task inputs were updated.
Before: Task input was App Configuration Name
After: Task input was updated to App Configuration endpoint. The App Configuration endpoint can be gotten from the App Configuration store overview page.
- Upgraded task to use Node 10. It previously used Node 6.
- Added the capability to use certificate based authentication.
- Added logs that show more details with reference to parameters used to run the task.
- Fixed a bug that caused the warning "Can't find loc string for key:CouldNotFetchAccessTokenforAzureStatusCode causes app config azdo task to fail" #520.
- Added the capability to use managed identity based authentication.
- Fixed incorrect tooltip help messages for task parameters in task editor UI #447
- Updated error message when certificate based authentication is used to indicate that it is not supported.
- Updated the readme
- Fixed an issue causing the task to partially succeed when key-values are overwritten #372
- Improved error message when required parameters are not provided
- Fixed an issue causing the task to fail when run in a Linux pipeline. #327
- Fixed the issue that some symbols, for example, percent sign (%), could not be set to Pipeline Task variables correctly. #313
- The Azure App Configuration pipeline task for the Azure DevOps is now generally available.
- Added
FAQ
section to the documentation.
- Added support for trimming key prefixes before setting as pipeline variables.
- Added support for resolving Key Vault references and setting as pipeline secrets.
-
Breaking change: With the support of Role-Based Access Control (RBAC) by the App Configuration service, the permission of this pipeline task can be granted with more granular and specific access control.
Before The Service Connection of this pipeline task is granted
Contributor
role in access control of the App Configuration store.After The Service Connection of this pipeline task is granted
Azure App Configuration Data Reader
role in access control of the App Configuration store.
- Fixed the issue that the
App Configuration name
dropdown is not populated if the App Configuration pipeline task is added to the pipeline YAML file via theassistant
UI of Tasks. #202
- Updated to use the authorization header syntax that is compliant with the REST API spec.
- Included API version for all requests sent to Azure App Configuration.
- Improved homepage documentation:
- Added a link to this release notes.
- Added an example of how to consume fetched key-values.
- Added support for auto-populated
App Configuration name
dropdown from a textbox. - Reset environment variables with invalid keys now prints a masked value,
****
, instead of the actual value of the key-value.
- Initial version.
- Added Azure App Configuration Extension to Azure DevOps Marketplace.
- Integrated with pipeline framework control
Azure subscription
so that user could use existingConnection Endpoint
to auth with Azure App Configuration instance. - Added support for
Key filter
andLabel
to query matched key-values.