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

Add self-referencing Swagger file to API Umbrella for Admin API #920

Closed
6 tasks
brylie opened this issue Apr 11, 2016 · 4 comments
Closed
6 tasks

Add self-referencing Swagger file to API Umbrella for Admin API #920

brylie opened this issue Apr 11, 2016 · 4 comments

Comments

@brylie
Copy link
Contributor

brylie commented Apr 11, 2016

We are currently maintaining a Meteor.js integration package for API Umbrella Admin API. When we started the project, the Admin API did not have significant documentation, nor a Swagger description file. The API Umbrella project now has a generic Swagger description file for the Admin API.

As an extension, we would like to use the swagger.js to automatically interface with an API Umbrella instance, so that we can deprecate our Meteor.js package. To this end, we have created an upstream feature request, and will begin working to provide this functionality as an upstream contribution.

Definition of done

  • Create/reuse a repository in apinf organization containing a fork of API Umbrella
  • Add modifications to the fork to meet the following criteria
    • API Umbrella should have a route to serve a self-referencing swagger.json
    • That swagger.json should document most or all Admin API endpoints
    • The swagger.json base URL should be set automatically to the current deployment URL
    • Optionally, use static documentation or autogenerate swagger.json

Resources

API Umbrella

Swagger / OpenAPI Spec

Apinf

@brylie brylie changed the title Add swagger generator to API Umbrella, for auto-documented Admin API Add self-referencing Swagger file to API Umbrella for Admin API Apr 11, 2016
@bajiat bajiat added the icebox label Jun 1, 2016
@brylie
Copy link
Contributor Author

brylie commented Aug 25, 2016

@bajiat this would still be useful for integration purposes. It might mean that we could deprecate our Meteor Swagger package in favor of using a generic Swagger API integration library.

@brylie
Copy link
Contributor Author

brylie commented Aug 25, 2016

Adding multi-proxy tag, since this is related to the API Umbrella integration.

@bajiat
Copy link
Contributor

bajiat commented Aug 25, 2016

@shaliko This is a task that would be immediately useful for us and probably requires looking at Api Umbrella source code. Could you look into this? If you wan more details, we can have a meeting or we can use chat to discuss. @brylie would be able to explain in more detail.

@shaliko
Copy link
Contributor

shaliko commented Aug 25, 2016

@bajiat @brylie OK, will be good have a meeting.

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

No branches or pull requests

4 participants