Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert ManageIQ REST API to leverage OpenAPI #19900

Open
chessbyte opened this issue Feb 28, 2020 · 5 comments
Open

Convert ManageIQ REST API to leverage OpenAPI #19900

chessbyte opened this issue Feb 28, 2020 · 5 comments

Comments

@chessbyte
Copy link
Member

This will enable the following

  • Auto-generated Clients
  • Auto-generated Documentation
  • GraphQL
@Fryguy
Copy link
Member

Fryguy commented Feb 28, 2020

@chessbyte chessbyte added this to Backlog in Roadmap Mar 18, 2020
@miq-bot
Copy link
Member

miq-bot commented Jun 11, 2020

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation.

@nateKlaux
Copy link

Do you still need rest API documentation in OAS??

@Fryguy
Copy link
Member

Fryguy commented Oct 12, 2020

@nateKlaux Yes, this issue is still open...ideally we can reuse the api.yml file somehow to "build" an OpenApi Specification file.

@nateKlaux
Copy link

@Fryguy Thanks for the response Jason! Sounds great. I'll try to allocate some time to research this further (hopefully) either today or tomorrow. Initial thoughts are hopeful that we can reuse the api.yml file, esp. if OAS was in mind during the creation of the API. :) Thanks for getting back to me, looking forward to helping out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Roadmap
  
Backlog
Development

No branches or pull requests

4 participants