Why plugin system is designed as using schema.json?

[monitor1379]

Problem: I am confused by why plugin system is designed as using file "api/conf/schema.json" instead of querying http://{apisix_host}:{control_port}/v1/schema when opening http://{apsix_dashboard_host}/plugin/market every time so can always get the newest plugin configs from apisix?

Documentation: FAQ/#4-after-modifying-the-plugin-schema-or-creating-a-custom-plugin-in-apache-apisix-why-cant-i-find-it-on-the-dashboard

Code of initSchema(): apisix-dashboard :: api/internal/conf/conf.go#L278-L285

[tokers]

The Control Plane itself shouldn't reply on an API exposed by the Data Plane, and CP doesn't have to know where the DP(s) are deployed.

Also, the Control APIs are designed to make some ops operation easy and they are helpful for troubleshooting.

[monitor1379]

Looks reasonable, now it's clear for me. thanks for answering! :D