[GitHub] [apisix-dashboard] moonming commented on issue #825: [Proposal]: Import & Export route from OpenAPI Specification3.0

[GitBox <gi...@apache.org>]

moonming commented on issue #825:
URL: https://github.com/apache/apisix-dashboard/issues/825#issuecomment-736271095


   > For the upstream info or service info which are not supported by OAS3.0, there are two feasible options of implementation scenarios:
   > 
   >     * Expand OAS3.0, increase `upstream` and `service`, which are required by APISIX, and at the same time provide a detailed documentation. we can refer to aliyun API gateway[1].
   >       
   >       * advantages:
   >         when users import OAS, they only need to pay attention to the profile and do not need to do any additional works.
   >         we can support batch operations.
   >         this also can be done only as a command-line tool.
   >       * disadvantages:
   >         Users need to modify the existing OAS refer to our doc.
   >         `upstream` and `service` are the only necessary expansiones, if we want to support other plugins by `import` operation, we also need to define new expansion.
   > 
   >     * Combine with existing create route page, when user create a route, they can import a OAS file, which provides parts of the route's info, and for the upstream 、 service and other plugins, they can follow the page step.
   >       
   >       * advantages:
   >         We don't need to expand OAS3.0.
   >         It can support all features supported by APISIX
   >       * disadvantages:
   >         We need to modify the current UE of create route to support this feature.
   > 
   > 
   > Reference:
   > [1]: https://help.aliyun.com/document_detail/88956.html?spm=a2c4g.11174283.6.564.7be17d24shSMBS
   > 
   > what do you think?
   > 
   > cc @juzhiyuan @gxthrj @LiteSun @nic-chen @membphis @moonming
   
   how can the user export it if using the second plan?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org