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

Proposal: Full lifecycle API management #611

Closed
1 of 5 tasks
juzhiyuan opened this issue Oct 28, 2020 · 7 comments
Closed
1 of 5 tasks

Proposal: Full lifecycle API management #611

juzhiyuan opened this issue Oct 28, 2020 · 7 comments
Assignees

Comments

@juzhiyuan
Copy link
Member

Please answer these questions before submitting your issue.

  • Why do you submit this issue?
  • Question or discussion
  • Bug
  • Requirements
  • Feature or performance improvement
  • Other

Requirements or improvement

  • Please describe your requirements or improvement suggestions.

TODO

@liuxiran
Copy link
Contributor

liuxiran commented Nov 5, 2020

Refactor features

  1. Publish and offline route.
    as discussed before, we could add a status field for route on APISIX, so If the solution remains the same, dashboard will add this function after apIsIx has added it.

  2. route online debug.
    we plan to use the previous implementation, import react-swagger-ui. Based on the original implementation, we will suppley the authentication and parameter verification part, so that the route online debug will become more complete and easy to use.
    Besides, we will add a new feature to generate apisdk, which would make it easy for users to dock the api published on the gateway

The feature to discuss

  1. For create route, we propose to add Import the export feature. import a route from openapi configuration, and export the route configuration compatible with openapi. It will be easier for the apis written with openapi specification to access the gateway.

  2. For publish route, we propose to introduce the concept of a publishing environment, e.g: test environment and Production environment. When a user publishes a route, they can choose the publishing environment. The benefit is that it makes it easy for users to adapt a set of routing designs to different operating environments, but at the same time, it introduces the burden of publishing environmental management.

  3. Permission control of the resource. Permission control of resources depends on user management, I wonder if we have plan to add this moudle.

cc @juzhiyuan @nic-chen @membphis @moonming

@membphis
Copy link
Member

membphis commented Nov 5, 2020

it is nice for me ^_^

@moonming
Copy link
Member

moonming commented Nov 6, 2020

3\. Permission control of the resource.  Permission control of resources depends on user management, I wonder if we have plan to add this moudle.

do you means RBAC?

@moonming
Copy link
Member

moonming commented Nov 6, 2020

@LiteSun please take a look

@liuxiran
Copy link
Contributor

liuxiran commented Nov 6, 2020

3\. Permission control of the resource.  Permission control of resources depends on user management, I wonder if we have plan to add this moudle.

do you means RBAC?

Yep, and this is also a feature that enterprise users need ☺️

@LiteSun
Copy link
Member

LiteSun commented Nov 18, 2020

Additional feature to discuss:

  1. Monitor Routes. [Proposal]: Monitor Routes #821
  2. Alarm Mechanism. [Proposal]: Alarm Mechanism #822
  3. Version management of route. [Proposal]: Version management of route #823

Technical details will be discussed in the corresponding proposal.

@juzhiyuan
Copy link
Member Author

This tracker issue could be closed.

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

No branches or pull requests

5 participants