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

   ### Issue description
   
   After updating the global plugin configuration and enabling the plugin, when 
disabling the plugin , the frontend cannot automatically restore the previous 
configuration information when re-enabling the plugin and needs to manually 
re-enter the configuration
   
   ### Expected behavior
   
   It is expected that when re-enabling the plugin, the frontend can 
automatically read and restore the previous configuration information without 
having to re-enter it.
   
   ### How to Reproduce
   
   1. Add a global plugin 
   2. Update the plugin configuration and enable the plugin 
   3. Disable the plugin, the configuration information is still obtained from 
the API  and etcd
   4. Re-enable the plugin, the frontend does not automatically restore the 
configuration information and needs to re-enter it.
   
   ### Screenshots
   
   _No response_
   
   ### Environment
   
   - apisix version (cmd: `apisix version`): **2.15**
   - 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:  **2.15**
   - Browser version, if have: **chrome 113.0.5672.127**
   
   
   ### Additional context
   
   This may be a bug where the frontend cannot automatically obtain existing 
plugin configuration information from the API and etcd. I hope the maintainer 
can locate and fix this issue to optimize the user experience of the global 
plugin configuration. I am also willing to provide further information to 
assist in debugging.
   Please check this issue and reply to confirm whether this is a valid bug 
report, as well as follow-up solutions or resolution times. Thank you! 
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to