Full Azure API Management suite and more VSTS extension
This software is provided as-is with no warranty of any kind.
API Management Suite in a nutshell
The purpose of this extension is to bring Azure API Management into VSTS as part of your release lifecyle. Whether you use API Management to monetize APIS or for internal purposes, it
is good to associate the release of your backends APIs with their corresponding facade APIs published against the API Gateway. On top of the API Management integration, the extension also
ships with an API Security Checker that helps validating that all endpoints of an API are well secured, this is of course only applicable to non-public APIs.
Support of OpenAPI v3
New task to create or update global policy.
ARM API version selector added to two of the tasks
New task to set policies on API operations. Kudos: Luis Ruiz Pavon
Ability to choose the Azure ARM API version to work with. Kudos:Jacques Snyman
It is now possible to push and restore the configuration to the underlying Git repo. Kudos:Justin Marshall
Security Groups get created on the fly when creating/updating products
APIs can be linked to multiple products Kudos:Luis Ruiz Pavon
Added the possibility to associate groups to products. Author: Luis Ruiz Pavon
New task to import legacy services from WSDL: SOAP Pass-Through and SOAP to REST. Author: Luis Ruiz Pavon
Minor improvements in the policy templates
Product creation task revisited to with visibility rules
Support of OAuth2 servers and OpenID Connect integration. Note that if you double check the authorization settings in the portal, you might need to refresh the page multiple times before it gets rendered correctly.
Switched the input type from "string" to "multiline" for policies
Added a new policy of type "custom"
Update of the documentation.
Supports versioned APIs
Creation of API products on the fly
Supports both API and Product policies
Supports the creation of APIs on top of Azure Functions
API Security checker
Setup prerequisite and considerations
In order to use this extension, you must have an ARM Service Endpoint configured in VSTS and make sure this endpoint is allowed to contribute to API Management instances. This can easily
be done by granting Subscription Contributor role or the ad-hoc API Management Service Contributor role. Similarly, the endpoint should have access to the Azure Functions should you plan to use the tasks related to Azure Functions.