The API Management team is excited to release two new features to help you manage your API Management service instances: Git access and Properties.
Each API Management service instance maintains a configuration database that contains information about the configuration and metadata for the service instance. Changes can be made to the service instance by modifying a setting in the publisher portal, using a PowerShell cmdlet, or making a REST API call. In addition to these methods, you can now manage your service instance configuration using Git, enabling service management scenarios such as:
- Configuration versioning: Download and store different versions of your service configuration
- Bulk configuration changes: Make changes to multiple parts of your service configuration in your local repository and integrate the changes back to the server with a single operation
- Familiar Git toolchain and workflow: Use the Git tooling and workflows you’re already familiar with
To manage your service instance using Git simply follow these steps.
- Enable Git access in your service.
- Save your service configuration database to your Git repository.
- Clone the Git repo to your local machine.
- Pull the latest repo down to your local machine and commit and push changes back to your repo.
- Deploy the changes from your repo into your service configuration database.
For more detailed step-by-step guidance on enabling and using Git access with your API Management service instances, see How to save and configure your API Management service configuration using Git.
With the release of API Management properties, each API Management service instance now has a properties collection of key/value pairs that are global to the service instance. These properties can be used to manage constant string values, including secrets, across all API configuration and policies.
Properties can contain literal strings, policy expressions and secrets. They can be used in API Management policies as complete or partial element and attribute values. Properties can be used to:
- Store any secrets used in policies outside of the policy statements themselves
- Store attribute values used in more than one policy and can be changed in one place if needed
To get started using properties, see How to use properties in Azure API Management policies.