> Another question, is it enough to just implement PUT/PATCH/GET/DELETE, just > like /global_rules?
this is enough. On Wed, Jan 20, 2021 at 3:58 PM Zexuan Luo <[email protected]> wrote: > Another question, is it enough to just implement PUT/PATCH/GET/DELETE, just > like /global_rules? > > Zexuan Luo <[email protected]> 于2021年1月19日周二 上午10:14写道： > > > > > - This idea is to reuse some common plugin configuration between > > routes. > > > > > > The solution contains several steps: > > 1. add namespace `/plugin_configs` > > Item in this namespace should have fields below: > > * id > > * name > > * plugins > > * create_time > > * update_time > > (Note: the arguments in plugins should pass the schema check.) > > > > 2. bind the plugin_config in route via plugin_config_id > > > > - 3. Like merging service, we merge the plugin_config into route when > > the route is hit. Note: should change route's modifiedIndex when > > plugin_config changed. When plugin_config and route has the same > plugin, > > the one from plugin_config will override the one in the route. > > > > > > What about your opinions? > > > > > -- *MembPhis* My GitHub: https://github.com/membphis Apache APISIX: https://github.com/apache/apisix
