Skip to content
A tool to convert an OpenAPI spec to its corresponding OMG spec
Python Dockerfile
Branch: master
Clone or download
Jude Pereira
Latest commit 669186e Aug 20, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
openapi2omg
Dockerfile Wrap into an OMG service. Aug 20, 2019
LICENSE
README.md
microservice.yaml Switch from a object to a map for properties (since the current omg t… Aug 20, 2019
requirements.txt
setup.py Prepare for packaging. Aug 12, 2019

README.md

openapi2omg

This tool aims to convert an OpenAPI 3 spec to its corresponding OMG equivalent. Not all features are supported, and some assumptions have been made. Please read the caveats section to understand these assumptions.

Storyscript

result = openapi2omg convert spec: openApiSpec properties: {"serverIndex": 0}

Caveats

Assumptions

  1. If there are multiple content types available for a given path, the content type application/json shall be preferred if available. If application/json is not available, then an appropriate content type will be chosen arbitrarily
  2. OMG doesn't support multiple responses. As such, the following order of response codes are considered as successful operations: 200, 201, 202, 2XX, 204, default. Furthermore, since multiple content types are not supported, application/json will be used if available. If application/json is not available, then an appropriate content type will be chosen arbitrarily

todos

related:

  1. https://github.com/microservices/microservice.guide/issues/50
  2. https://github.com/microservices/microservice.guide/pull/96

License

MIT License

You can’t perform that action at this time.