You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2020/09/22 02:09:18 UTC

[GitHub] [apisix-dashboard] juzhiyuan opened a new issue #498: Use Admin API directly instead of Manager API (frontend)

juzhiyuan opened a new issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498


   As titled


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] juzhiyuan commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-699639025


   > > @juzhiyuan
   > > For API parameters, please refer to: https://github.com/apache/apisix/blob/master/doc/admin-api.md
   > 
   > I'd like to know only APIs listed in this file have been implemented? how about those APIs?
   > 
   > 1. `/notexist/routes`
   > 2. `/names/routegroups`
   > 3. `/names/upstreams`
   > 4. `check_ssl_exists`
   > 
   > etc
   
   1. `/notexist/routes`: to check if there has an existing route with same name? (maybe, cc @nic-chen)
   2. `/names/routegroups`: check if there has a group with the same name
   3. `/names/upstreams`: xxx
   4. `check_ssl_exists`: to check if there has a related host with SSL certificate.
   5. `check_ssl_cert`: to check if the Key and Cert could be compared, and it will return the encrypted data from Certificate.
   6. xxx Not sure if there have other APIs.


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] juzhiyuan closed issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
juzhiyuan closed issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498


   


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] juzhiyuan commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-697101592


   @nic-chen will help to deal with the issue about "How to resolve those fields in MySQL".
   
   cc @liuxiran


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] ShiningRush edited a comment on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
ShiningRush edited a comment on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-699629286


   > I'd like to know only APIs listed in this file have been implemented? how about those APIs?
   
   Here is anyone can tell me what those apis used for? then I can consider how to implement it in new architecture : )


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] juzhiyuan commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-696473955


   @nic-chen @ShiningRush Please deploy an API Server before 27/09/2020.


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] liuxiran commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
liuxiran commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-697228390


   > 2. route group
   >    I think `labels` is enough for us to group routes or other stuff.
   >    what do you think?  @liuxiran @membphis
   
   Agree 😊, It would be more flexible.
   
   >I had checked other sql schema, I think we don’t need to deal with other columns that existed in mysql and not in etcd >temporarily, such as create_time, update_time.
   
   Some users may be concerned about the update time, so that they can trace a resource changes.
   so if these fields would not be stored in etcd, maybe it still needs a place where the front end can get it. what do you think? @juzhiyuan @LiteSun 
   


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] ShiningRush edited a comment on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
ShiningRush edited a comment on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-699629286


   > I'd like to know only APIs listed in this file have been implemented? how about those APIs?
   
   Here is anyone can tell me what those apis used for? 


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] nic-chen edited a comment on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
nic-chen edited a comment on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-697202232


   We have three problems to solve:
   1. publish and offline
   as discussed before, we could implement this feature on APISIX
   
   2. route group
   I think `labels` is enough for us to group routes or other stuff.
   what do you think?  @liuxiran @membphis  
   
   3. relational database features
   such as:
   https://github.com/apache/apisix-dashboard/issues/466
   
   
   I had checked other sql schema, I think we don’t need to deal with other columns that existed in mysql and not in etcd temporarily, such as `create_time`, `update_time`.
   
   
   


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] juzhiyuan commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-697286151


   What do you think? @nic-chen @membphis @ShiningRush 


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] nic-chen commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
nic-chen commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-697202232


   We have three problems to solve:
   1. publish and offline
   as discussed before, we could implement this feature on APISIX
   
   2. route group
   I think `labels` is enough for us to group routes or other stuff.
   what do you think?  @liuxiran @membphis  
   
   3. relational database features
   such as:
   https://github.com/apache/apisix-dashboard/issues/466
   
   
   
   


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] juzhiyuan commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-699616533


   It means all features related to those APIs will be removed from frontend..


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] ShiningRush commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
ShiningRush commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-699629286


   > I'd like to know only APIs listed in this file have been implemented? how about those APIs?
   Here is anyone can tell me what those apis used for? 


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] juzhiyuan commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-699612760


   > @juzhiyuan
   > For API parameters, please refer to: https://github.com/apache/apisix/blob/master/doc/admin-api.md
   
   I'd like to know only APIs listed in this file have been implemented? how about those APIs?
   1. `/notexist/routes`
   2. `/names/routegroups`
   3. `/names/upstreams`
   4. `check_ssl_exists`
   
   etc


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] juzhiyuan commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-696473955


   @nic-chen @ShiningRush Please deploy an API Server before 27/09/2020.


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] nic-chen commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
nic-chen commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-699614196


   not support relational query yet, so these APIs can't be implemented, and it will take some time
   


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] nic-chen commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
nic-chen commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-699611624


   @juzhiyuan 
   For API parameters, please refer to: https://github.com/apache/apisix/blob/master/doc/admin-api.md
   


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] nic-chen commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
nic-chen commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-699611434


   @juzhiyuan  
   I had deployed a online demo for refactored manager api, here is the host and port: 40.73.92.163:8080
   
   but there are some problems, such as: 
   https://github.com/apache/apisix-dashboard/issues/519
   that means you need to specify a ID when create resource.
   
   
   


----------------------------------------------------------------
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

[GitHub] [apisix-dashboard] juzhiyuan commented on issue #498: Use Admin API directly instead of Manager API (frontend)

Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on issue #498:
URL: https://github.com/apache/apisix-dashboard/issues/498#issuecomment-696473955






----------------------------------------------------------------
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