/odata-openapi

Worked example of wrapping the OASIS OData TC in a simple JS SPA. With some additional extensions of post-processing the OpenAPI content to tailor SAP Gateway conversions for either Azure APIM import or for use with PowerPlatform.

Primary LanguageXSLTOtherNOASSERTION

📖Introduction

This work is a simple hosting container for the OASIS OData-openapi js executable wrapped in a nodeJs running Azure Function App. In addition to OpenAPI conversion it offers OData metadata JSON translation based of the OASIS odata-json-schema repos.

It exists solely to demonstrate how to provide a simple HTML5 wrapper around the OASIS code repository, primarily for the purpose of making it easier to work with SAP OData services and their XML metadata when wanting to publish them through Azure API Management.

💡How-To

You can see it in action, convert OData definitions to OpenAPI specifications here, and generate SDKs for popular programming languages.

Find more details on the SDK generation on the Kiota website. We decided to use Kiota instead of AutoREST because of its greater flexibility for our project.

Please feel free to deploy it yourself via a combination of a Azure Functions Consumption App (Source is in the /FunctionApp/ folder) and a web-enabled Azure Storage Account (Source is in the /SPA/ folder).

🪂Deploy Function App

You can deploy the Function App to an existing app via the Azure CLI using the following command:

func azure functionapp publish ODataToOpenAPI3Converter

🤟🏾Contributing

Please raise any issues and feature requests via Github Issues.