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:
- 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.