Support import of API definitions and metadata from OData $metadata.
Allen Peterson commented
We have been using odata as our endpoints for our internal api services and serving them through Azure Api Manager. Now, we would like to have $metadata available as an option in the Azure Api Manager like we can for Open Api (JSON or YAML). Is there a plan for this to support metadata consumption from api manager directly?
Jorulf Beitland commented
We are evaluating Azure API Mngt versus SAP Cloud Platform API Mngt. This is one if the biggest issues why we score SAPs solution as better. SAP is heavily dependend on OData and their ability to automatically import metadata from OData is excellent.
Micah Rairdon commented
Oasis-tcs that maintains the ODATA standard does keep an xsl up to date for converting odata metadata to OpenAPI spec. This should allow importing of an odata metatadata if you use the xsl on the backend to convert it to OpenAPI
Maqsood Ali commented
we are building oData api, but one thing we are thinking to produce swagger for our oData base api so that we can import into Azure api management. Any experience or tooling available for it which can also be automated (continuous delivery) using visual studio team services.
Chris Lundy commented
We wold also like to have Odata support in Azure API Management Gateway. We have many Microsoft tools and are part of a multi-billion dollar retail business. We are evaluating this tool vs Apigee, BlueMix and Mashery. I would expect Microsoft support its own standards. Odata is part of Online, CRM, etc. At least support it until you phase it out.
We also need to import SAP backend services and the SAP Gateway uses OData, importing the edmx file directly into APIM (instead of converting into to swagger) would be very useful.
10 thumbs up! Please import Odata automatically based on $metadata tag
Frederik-Jan Roose commented
We want to put Azure APIM in front of SAP applications to easily expose some functionality. As SAP exposes all their services as OData this support would be very useful if it could be integrated in a standard way (not with the workaround).
We need it also... It will be very helpful if it works!
John Phillips commented
Support creating an OData v4 API to support Web API OData v4 operations.
Generating the API based on the OData metadata would be optimal.
The rest of the features of APIM would apply as they do to any API we create.
Greg Scull commented
Please!!!! We have a OData v4 service which I would like to expose this way. Currently I have to parse the $metadata URL into swagger and then import to get it to show up. While it works (so far so good) it really should let me point to the metadata URL and then customize access to the OData Controllers (public subset of the full OData services we consume internally)