moonming commented on a change in pull request #2744:
URL: https://github.com/apache/apisix/pull/2744#discussion_r523419060
##########
File path: doc/architecture-design.md
##########
@@ -188,7 +188,7 @@ Note: When both Route and Service enable the same plugin,
the Route parameter ha
The `Plugin` configuration can be bound directly to `Route` or it can be bound
to `Service` or `Consumer`. For the configuration of the same plugin, only one
copy is valid, and the configuration selection priority is always `Consumer` >
`Route` > `Service`.
-In `conf/config.yaml`, you can declare which plugins are supported by the
local APISIX node. This is a whitelisting mechanism. Plugins that are not in
this whitelist will be automatically ignored. This feature can be used to
temporarily turn off or turn on specific plugins, which is very effective in
dealing with unexpected situations.
+In `conf/config.yaml`, you can declare which plugins are supported by the
local APISIX node. This is a whitelisting mechanism. Plugins that are not in
this whitelist will be automatically ignored. This feature can be used to
temporarily turn off or turn on specific plugins, which is very effective in
dealing with unexpected situations. If you want to add new plugins based on
existing plugins, you need to copy the `plugins` node content of
`config-default.yaml` to the `plugins` node of `conf/config.yaml`.
Review comment:
why we need copy configure file? @membphis
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
