Please answer these questions before submitting your issue.
TODO
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.
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
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.
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.
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
it is nice for me ^_^
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?
@LiteSun please take a look
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 鈽猴笍
Additional feature to discuss:
Technical details will be discussed in the corresponding proposal.
This tracker issue could be closed.
Most helpful comment
Refactor features
Publish and offline route.
as discussed before, we could add a
statusfield for route on APISIX, so If the solution remains the same, dashboard will add this function after apIsIx has added it.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
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.
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.
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