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 2022/04/08 09:21:56 UTC

[GitHub] [apisix-dashboard] kevinw66 opened a new issue, #2415: When route choose to use plugin_configs, the export/import has a bug

kevinw66 opened a new issue, #2415:
URL: https://github.com/apache/apisix-dashboard/issues/2415

   ### Issue description
   
   When I add plugin_configs and add it in route, before export the route, the route data is like below
   ![image](https://user-images.githubusercontent.com/31196226/162406215-7469c150-bce5-4ff9-b7e4-4cf3dfd1c1fa.png)
   
   And after I import the route, I got this data
   ![image](https://user-images.githubusercontent.com/31196226/162406271-4eb9627d-39e9-4fe0-9524-4daeb0f25d78.png)
   
   BTW, I didn't use `request-validation` plugin in plugin_configs
   
   ### Expected behavior
   
   described in description
   
   ### How to Reproduce
   
   described in description
   
   ### Screenshots
   
   _No response_
   
   ### Environment
   
   - apisix version (cmd: `apisix version`):
   - OS (cmd: `uname -a`):
   - OpenResty / Nginx version (cmd: `nginx -V` or `openresty -V`):
   - etcd version, if have (cmd: run `etcd --version`):
   - apisix-dashboard version, if have:
   - Browser version, if have:
   
   
   ### Additional context
   
   _No response_


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

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org.apache.org

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

[GitHub] [apisix-dashboard] kevinw66 commented on issue #2415: When route choose to use plugin_configs, the export/import has a bug

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

   Suggestion:
   Can we simply export data in etcd instead of openapi?
   Because currently if our route bind with service or upstream, after we export/import the route, the service or upstream config will be removed and set in route directly.
   When we sync config from different environment, this is not we wanted, we also want sync the service and upstream config.
   But through openapi, it's complicated. And this can be easily done with export json data in etcd.


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

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

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

[GitHub] [apisix-dashboard] kevinw66 commented on issue #2415: When route choose to use plugin_configs, the export/import has a bug

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

   And I saw few methods was deleted after import


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

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

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