request help: use the disable property to disable plugin

[juzhiyuan]

Issue description

Should we update plugins' docs to use the disable property instead of omitting the plugin's data to disable that plugin? This could prevent lost plugin's data when disabling it.

e.g https://github.com/apache/apisix/blob/master/doc/plugins/api-breaker.md#disable-plugin

Environment

• apisix version (cmd: apisix version): No
• OS: No

[membphis]

We can add a new section about this way, add a reference to the doc of plugin.

[spacewander]

Isn't this behavior broken now? Add a disable field doesn't trigger the destory method of the plugin. And re-enable a plugin doesn't the init method.

[spacewander]

Better not mention this experimental feature in the doc.

[spacewander]

OK, I was misled right now. It is disable a plugin for a route/service, not disable a plugin. We should clarify it in the doc. The current doc mess enable / disable a plugin for a route/service with enable / disable a plugin, and many people are mislead.

[spacewander]

I think the plugins' doc need to be rewritten to show the difference. There is no need to show the disable a plugin for a route/service in every doc since they are similar.

[juzhiyuan]

https://github.com/apache/apisix-dashboard/pull/898/files#diff-0dc947a149da358540c612806141422ec2dab3029fcc1b255953be994655ec74R151-R160

This PR[1] would depend on this feature, related issue [2]

[1] apache/apisix-dashboard#898
[2] apache/apisix-dashboard#495

[spacewander]

Done.