avinal commented on a change in pull request #6464:
URL: https://github.com/apache/apisix/pull/6464#discussion_r815860605
##########
File path: docs/en/latest/architecture-design/plugin.md
##########
@@ -21,17 +21,21 @@ title: Plugin
#
-->
-`Plugin` represents the plugin configuration that will be executed during the
`HTTP` request/response lifecycle.
+This represents the configuration of the plugins that are executed during the
HTTP request/response lifecycle.
-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`.
+A `Plugin` configuration can be bout directly to a [`Route`](./route.md), a
[`Service`](./service.md) or a [`Consumer`](./consumer.md).
-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 data of `plugins` node which in
`conf/config-default.yaml` to the `plugins` node of `conf/config.yaml`.
+Note: While configuring the same plugin, only one copy of the configuration is
valid. The order of precedence is always `Consumer` > `Route` > `Service`.
Review comment:
```suggestion
**Note**: While configuring the same plugin, only one copy of the
configuration is valid. The order of precedence is always `Consumer` > `Route`
> `Service`.
```
--
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]
