This is an automated email from the ASF dual-hosted git repository.
Yilialinn pushed a commit to branch release/3.15
in repository https://gitbox.apache.org/repos/asf/apisix.git
The following commit(s) were added to refs/heads/release/3.15 by this push:
new 029e0c7b0d docs: fix malformed plugin table rendering in 3.15 (#13967)
029e0c7b0d is described below
commit 029e0c7b0dbc07f249d61dcbb2ca1064b40a2318
Author: Yilia Lin <[email protected]>
AuthorDate: Fri Sep 18 13:53:33 2026 +0800
docs: fix malformed plugin table rendering in 3.15 (#13967)
---
docs/en/latest/plugins/aws-lambda.md | 8 ++++----
docs/en/latest/plugins/prometheus.md | 6 +++---
docs/zh/latest/plugins/aws-lambda.md | 10 +++++-----
docs/zh/latest/plugins/grpc-transcode.md | 2 +-
docs/zh/latest/plugins/loki-logger.md | 4 ++--
docs/zh/latest/plugins/prometheus.md | 6 +++---
docs/zh/latest/plugins/rocketmq-logger.md | 4 ++--
docs/zh/latest/plugins/traffic-split.md | 2 +-
8 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/docs/en/latest/plugins/aws-lambda.md
b/docs/en/latest/plugins/aws-lambda.md
index f9344859d4..c13cf23fb5 100644
--- a/docs/en/latest/plugins/aws-lambda.md
+++ b/docs/en/latest/plugins/aws-lambda.md
@@ -43,10 +43,10 @@ This Plugin supports authorization via AWS API key and AWS
IAM secrets. The Plug
| authorization | object | False | | |
Authorization credentials to access the cloud function.
|
| authorization.apikey | string | False | | |
Generated API Key to authorize requests to the AWS Gateway endpoint.
|
| authorization.iam | object | False | | | Used
for AWS IAM role based authorization performed via AWS v4 request signing. See
[IAM authorization schema](#iam-authorization-schema). |
-| authorization.iam.accesskey | string | True | | Generated
access key ID from AWS IAM console. |
-| authorization.iam.secretkey | string | True | | Generated
access key secret from AWS IAM console. |
-| authorization.iam.aws_region | string | False | "us-east-1" | AWS
region where the request is being sent.
|
-| authorization.iam.service | string | False | "execute-api" | The
service that is receiving the request. For Amazon API gateway APIs, it should
be set to `execute-api`. For Lambda function, it should be set to `lambda`. |
+| authorization.iam.accesskey | string | True | |
| Generated access key ID from AWS IAM console.
|
+| authorization.iam.secretkey | string | True | |
| Generated access key secret from AWS IAM console.
|
+| authorization.iam.aws_region | string | False | "us-east-1" |
| AWS region where the request is being sent.
|
+| authorization.iam.service | string | False | "execute-api" |
| The service that is receiving the request. For Amazon API gateway APIs, it
should be set to `execute-api`. For Lambda function, it should be set to
`lambda`. |
| timeout | integer | False | 3000 | [100,...] | Proxy
request timeout in milliseconds.
|
| ssl_verify | boolean | False | true | true/false | When
set to `true` performs SSL verification.
|
| keepalive | boolean | False | true | true/false | When
set to `true` keeps the connection alive for reuse.
|
diff --git a/docs/en/latest/plugins/prometheus.md
b/docs/en/latest/plugins/prometheus.md
index d64355fdda..dbf8ff4cb7 100644
--- a/docs/en/latest/plugins/prometheus.md
+++ b/docs/en/latest/plugins/prometheus.md
@@ -158,7 +158,7 @@ The following labels are used to differentiate
`apisix_bandwidth` metrics.
### Labels for `apisix_llm_latency`
| Name | Description
|
-| ---------- |
-----------------------------------------------------------------------------------------------------------------------------
|
|
+| ---------- |
-----------------------------------------------------------------------------------------------------------------------------
|
| route_id | ID of the Route that bandwidth corresponds to when
`prefer_name` is `false` (default), and name of the Route when `prefer_name` to
`true`. Default to an empty string if a request does not match any Route.
|
| service_id | ID of the Service that bandwidth corresponds to when
`prefer_name` is `false` (default), and name of the Service when `prefer_name`
to `true`. Default to the configured value of host on the Route if the matched
Route does not belong to any Service. |
| consumer | Name of the Consumer associated with a request. Default to an
empty string if no Consumer is associated with the request.
|
@@ -184,7 +184,7 @@ The following labels are used to differentiate
`apisix_bandwidth` metrics.
### Labels for `apisix_llm_completion_tokens`
| Name | Description
|
-| ---------- |
-----------------------------------------------------------------------------------------------------------------------------
|
|
+| ---------- |
-----------------------------------------------------------------------------------------------------------------------------
|
| route_id | ID of the Route that bandwidth corresponds to when
`prefer_name` is `false` (default), and name of the Route when `prefer_name` to
`true`. Default to an empty string if a request does not match any Route.
|
| service_id | ID of the Service that bandwidth corresponds to when
`prefer_name` is `false` (default), and name of the Service when `prefer_name`
to `true`. Default to the configured value of host on the Route if the matched
Route does not belong to any Service. |
| consumer | Name of the Consumer associated with a request. Default to an
empty string if no Consumer is associated with the request.
|
@@ -195,7 +195,7 @@ The following labels are used to differentiate
`apisix_bandwidth` metrics.
### Labels for `apisix_llm_prompt_tokens`
| Name | Description
|
-| ---------- |
-----------------------------------------------------------------------------------------------------------------------------
|
|
+| ---------- |
-----------------------------------------------------------------------------------------------------------------------------
|
| route_id | ID of the Route that bandwidth corresponds to when
`prefer_name` is `false` (default), and name of the Route when `prefer_name` to
`true`. Default to an empty string if a request does not match any Route.
|
| service_id | ID of the Service that bandwidth corresponds to when
`prefer_name` is `false` (default), and name of the Service when `prefer_name`
to `true`. Default to the configured value of host on the Route if the matched
Route does not belong to any Service. |
| consumer | Name of the Consumer associated with a request. Default to an
empty string if no Consumer is associated with the request.
|
diff --git a/docs/zh/latest/plugins/aws-lambda.md
b/docs/zh/latest/plugins/aws-lambda.md
index 7b23a355a4..e2cb9b8b72 100644
--- a/docs/zh/latest/plugins/aws-lambda.md
+++ b/docs/zh/latest/plugins/aws-lambda.md
@@ -38,15 +38,15 @@ description: 本文介绍了关于 Apache APISIX aws-lambda 插件的基本信
## 属性
| 名称 | 类型 | 必选项 | 默认值 | 有效值 | 描述
|
-| ------------------ - | ------- | -------- | ------- | ------------ |
------------------------------------------------------------ |
+| -------------------- | ------- | -------- | ------- | ------------ |
------------------------------------------------------------ |
| function_uri | string | 是 | | | 触发
lambda serverless 函数的 AWS API Gateway 端点。 |
| authorization | object | 否 | | |
访问云函数的授权凭证。 |
| authorization.apikey | string | 否 | | | 生成的 API
密钥，用于授权对 AWS Gateway 端点的请求。 |
| authorization.iam | object | 否 | | | 用于通过 AWS
v4 请求签名执行的基于 AWS IAM 角色的授权。请参考 [IAM 授权方案](#iam-授权方案)。 |
-| authorization.iam.accesskey | string | 是 | | 从 AWS IAM
控制台生成的访问密钥 ID。 |
-| authorization.iam.secretkey | string | 是 | | 从 AWS IAM
控制台生成的访问密钥。 |
-| authorization.iam.aws_region | string | 否 | "us-east-1" | 发出请求的 AWS
区域。有关更多 AWS 区域代码的信息请参考 [AWS
区域代码表](https://docs.aws.amazon.com/zh_cn/general/latest/gr/rande.html#region-names-codes)。
|
-| authorization.iam.service | string | 否 | "execute-api" |
接收该请求的服务。若使用 Amazon API gateway APIs, 应设置为 `execute-api`。若使用 Lambda function,
应设置为 `lambda`。 |
+| authorization.iam.accesskey | string | 是 | |
| 从 AWS IAM 控制台生成的访问密钥 ID。 |
+| authorization.iam.secretkey | string | 是 | |
| 从 AWS IAM 控制台生成的访问密钥。 |
+| authorization.iam.aws_region | string | 否 | "us-east-1" |
| 发出请求的 AWS 区域。有关更多 AWS 区域代码的信息请参考 [AWS
区域代码表](https://docs.aws.amazon.com/zh_cn/general/latest/gr/rande.html#region-names-codes)。
|
+| authorization.iam.service | string | 否 | "execute-api" |
| 接收该请求的服务。若使用 Amazon API gateway APIs, 应设置为 `execute-api`。若使用 Lambda
function, 应设置为 `lambda`。 |
| timeout | integer | 否 | 3000 | [100,...] |
代理请求超时（以毫秒为单位）。 |
| ssl_verify | boolean | 否 | true | true/false | 当设置为
`true` 时执行 SSL 验证。 |
| keepalive | boolean | 否 | true | true/false | 当设置为
`true` 时，保持连接的活动状态以便重复使用。 |
diff --git a/docs/zh/latest/plugins/grpc-transcode.md
b/docs/zh/latest/plugins/grpc-transcode.md
index 10052d7d08..223a288611 100644
--- a/docs/zh/latest/plugins/grpc-transcode.md
+++ b/docs/zh/latest/plugins/grpc-transcode.md
@@ -39,7 +39,7 @@ APISIX 接收 HTTP 请求后，首先对请求进行转码，并将转码后的
## 属性
| 名称 | 类型
| 必选项 | 默认值 | 描述 |
-| --------- | ------------------------------------------------- | ----- |
------ ------------------------------ |
+| --------- | -------------------------------------------------- | ----- |
------ | -------------------------------------- |
| proto_id | string/integer | 是 |
| `.proto` 内容的 id。 |
| service | string | 是 |
| gRPC 服务名。 |
| method | string | 是 |
| gRPC 服务中要调用的方法名。 |
diff --git a/docs/zh/latest/plugins/loki-logger.md
b/docs/zh/latest/plugins/loki-logger.md
index 3cff508700..494e8aa500 100644
--- a/docs/zh/latest/plugins/loki-logger.md
+++ b/docs/zh/latest/plugins/loki-logger.md
@@ -41,7 +41,7 @@ description: loki-logger 插件通过 Loki HTTP API /loki/api/v1/push
将请求
## 属性
| 名称 | 类型 | 必选项 | 默认值 | 有效值 | 描述 |
-|--|---|---|---|---|
+| --- | --- | --- | --- | --- | --- |
| end_addrs | array[string] | 是 | | | Loki API URL，例如
`http://127.0.0.1:3100`。如果配置了多个端点，日志将被推送到列表中随机确定的端点。 |
| end_uri | string | 否 | /loki/api/v1/push | | Loki 提取端点的 URI 路径。 |
| tenant_id | string | 否 | fake | | Loki 租户 ID。根据 Loki 的
[多租户文档](https://grafana.com/docs/loki/latest/operations/multi-tenancy/#multi-tenancy)，在单租户下默认值设置为
`fake`。 |
@@ -68,7 +68,7 @@ description: loki-logger 插件通过 Loki HTTP API /loki/api/v1/push
将请求
| 名称 | 类型 | 必选项 | 默认值 | 描述 |
|------|------|----------|--|-------------|
| log_format | object | 否 | | 日志格式以 JSON
的键值对声明。值支持字符串和嵌套对象（最多五层，超出部分将被截断）。字符串中可通过在前面加上 `$` 来引用 [APISIX
变量](../apisix-variable.md) 和 [NGINX
变量](http://nginx.org/en/docs/varindex.html)。 |
-| max_pending_entries | integer | 否 | | | 在批处理器中开始删除待处理条目之前可以购买的最大待处理条目数。|
+| max_pending_entries | integer | 否 | | 在批处理器中开始删除待处理条目之前可以购买的最大待处理条目数。|
## 示例
diff --git a/docs/zh/latest/plugins/prometheus.md
b/docs/zh/latest/plugins/prometheus.md
index 21361e3581..d9f4251d12 100644
--- a/docs/zh/latest/plugins/prometheus.md
+++ b/docs/zh/latest/plugins/prometheus.md
@@ -158,7 +158,7 @@ Prometheus 中有不同类型的指标。要了解它们之间的区别，请参
### Labels for `apisix_llm_latency`
| Name | Description
|
-| ---------- |
-----------------------------------------------------------------------------------------------------------------------------
|
|
+| ---------- |
-----------------------------------------------------------------------------------------------------------------------------
|
| route_id | 带宽对应的路由 ID，当 `prefer_name` 为 `false`（默认）时，使用路由 ID，当
`prefer_name` 为 `true` 时，使用路由名称。如果请求不匹配任何路由，则默认为空字符串。 |
| service_id | 带宽对应的服务 ID，当 `prefer_name` 为 `false`（默认）时，使用服务 ID，当
`prefer_name` 为 `true` 时，使用服务名称。如果匹配的路由不属于任何服务，则默认为路由上配置的主机值。 |
| consumer | 与请求关联的消费者名称。如果请求没有与之关联的消费者，则默认为空字符串。 |
@@ -184,7 +184,7 @@ Prometheus 中有不同类型的指标。要了解它们之间的区别，请参
### Labels for `apisix_llm_completion_tokens`
| Name | Description
|
-| ---------- |
-----------------------------------------------------------------------------------------------------------------------------
|
|
+| ---------- |
-----------------------------------------------------------------------------------------------------------------------------
|
| route_id | 带宽对应的路由 ID，当 `prefer_name` 为 `false`（默认）时，使用路由 ID，当
`prefer_name` 为 `true` 时，使用路由名称。如果请求不匹配任何路由，则默认为空字符串。 |
| service_id | 带宽对应的服务 ID，当 `prefer_name` 为 `false`（默认）时，使用服务 ID，当
`prefer_name` 为 `true` 时，使用服务名称。如果匹配的路由不属于任何服务，则默认为路由上配置的主机值。 |
| consumer | 与请求关联的消费者名称。如果请求没有与之关联的消费者，则默认为空字符串。 |
@@ -195,7 +195,7 @@ Prometheus 中有不同类型的指标。要了解它们之间的区别，请参
### Labels for `apisix_llm_prompt_tokens`
| Name | Description
|
-| ---------- |
-----------------------------------------------------------------------------------------------------------------------------
|
|
+| ---------- |
-----------------------------------------------------------------------------------------------------------------------------
|
| route_id | 带宽对应的路由 ID，当 `prefer_name` 为 `false`（默认）时，使用路由 ID，当
`prefer_name` 为 `true` 时，使用路由名称。如果请求不匹配任何路由，则默认为空字符串。 |
| service_id | 带宽对应的服务 ID，当 `prefer_name` 为 `false`（默认）时，使用服务 ID，当
`prefer_name` 为 `true` 时，使用服务名称。如果匹配的路由不属于任何服务，则默认为路由上配置的主机值。 |
| consumer | 与请求关联的消费者名称。如果请求没有与之关联的消费者，则默认为空字符串。 |
diff --git a/docs/zh/latest/plugins/rocketmq-logger.md
b/docs/zh/latest/plugins/rocketmq-logger.md
index c421b148c1..7aa0ba32e0 100644
--- a/docs/zh/latest/plugins/rocketmq-logger.md
+++ b/docs/zh/latest/plugins/rocketmq-logger.md
@@ -34,7 +34,7 @@ description: API 网关 Apache APISIX 的 rocketmq-logger 插件用于将日志
## 属性
| 名称 | 类型 | 必选项 | 默认值 | 有效值 |
描述 |
-| ---------------------- | ------- | ------ | ---------------- |
------------- ------- | ------------------------------------------------ |
+| ---------------------- | ------- | ------ | ----------------- |
--------------------- | ------------------------------------------------ |
| nameserver_list | object | 是 | |
| RocketMQ 的 nameserver 列表。 |
| topic | string | 是 | |
| 要推送的 topic 名称。 |
| key | string | 否 | |
| 发送消息的 keys。 |
@@ -123,7 +123,7 @@ description: API 网关 Apache APISIX 的 rocketmq-logger 插件用于将日志
| 名称 | 类型 | 必选项 | 默认值
| 描述
|
|------------|--------|-----|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| log_format | object | 否 | | 日志格式以 JSON
的键值对声明。值支持字符串和嵌套对象（最多五层，超出部分将被截断）。字符串中可通过在前面加上 `$` 来引用 [APISIX
变量](../../../en/latest/apisix-variable.md) 或 [NGINX
内置变量](http://nginx.org/en/docs/varindex.html)。 |
-| max_pending_entries | integer | 否 | | | 在批处理器中开始删除待处理条目之前可以购买的最大待处理条目数。|
+| max_pending_entries | integer | 否 | | 在批处理器中开始删除待处理条目之前可以购买的最大待处理条目数。|
:::note 注意
diff --git a/docs/zh/latest/plugins/traffic-split.md
b/docs/zh/latest/plugins/traffic-split.md
index a460d4bfcb..691c87d1ad 100644
--- a/docs/zh/latest/plugins/traffic-split.md
+++ b/docs/zh/latest/plugins/traffic-split.md
@@ -45,7 +45,7 @@ description: traffic-split 插件根据条件和/或权重将流量引导至各
## 属性
| 名称 | 类型 | 必选项 | 默认值 | 有效值 | 描述 |
-| ---------------------- | --------------| ------ | ------ | ------
|--------------------------------------------------------
--------------------------------------------------
--------------------------------------------------
--------------------------------------------------
--------------------------------------------------|
+| ---------------------- | -------------- | ------ | ------ | ------ |
------------------------------------------------------- |
| rules.match | array[object] | 否 | | | 要执行的一对或多对匹配条件和操作的数组。 |
| rules.match | array[object] | 否 | | | 条件流量分割的匹配规则。 |
| rules.match.vars | array[array] | 否 | | | 以
[lua-resty-expr](https://github.com/api7/lua-resty-expr#operator-list)
形式包含一个或多个匹配条件的数组，用于有条件地执行插件。 |
