@leaflow/sdk 0.54.3 → 0.55.0

package/dist/index.d.ts

@@ -4,6 +4,7 @@ export type * as billing from "./billing/v1/index.js";
 export type * as canopy from "./canopy/v1/index.js";
 export type * as compute from "./compute/v1/index.js";
 export type * as dns from "./dns/v1/index.js";
+export type * as fleet from "./fleet/v1/index.js";
 export type * as iam from "./iam/v1/index.js";
 export type * as monitoring from "./monitoring/v1/index.js";
 export type * as notification from "./notification/v1/index.js";

package/dist/monitoring/v1/index.d.ts

@@ -66,14 +66,14 @@ export type ListServersResult = operations["list-servers"]["responses"][200]["co
 export type ListServersQuery = operations["list-servers"]["parameters"]["query"];
 /** `GET /api/v1/servers/{serverId}` 成功时的响应体。 */
 export type GetServerResult = operations["get-server"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/servers/{serverId}` 成功时的响应体。 */
-export type UpdateServerResult = operations["update-server"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/servers/{serverId}` 的请求体。 */
-export type UpdateServerBody = NonNullable<operations["update-server"]["requestBody"]>["content"]["application/json"];
 /** `PUT /api/v1/servers/{serverId}` 成功时的响应体。 */
 export type EnableServerMonitoringResult = operations["enable-server-monitoring"]["responses"][200]["content"]["application/json"];
 /** `PUT /api/v1/servers/{serverId}` 的请求体。 */
 export type EnableServerMonitoringBody = NonNullable<operations["enable-server-monitoring"]["requestBody"]>["content"]["application/json"];
+/** `PATCH /api/v1/servers/{serverId}` 成功时的响应体。 */
+export type UpdateServerResult = operations["update-server"]["responses"][200]["content"]["application/json"];
+/** `PATCH /api/v1/servers/{serverId}` 的请求体。 */
+export type UpdateServerBody = NonNullable<operations["update-server"]["requestBody"]>["content"]["application/json"];
 /** `POST /api/v1/servers/{serverId}/psk` 成功时的响应体。 */
 export type RotateAgentPskResult = operations["rotate-agent-psk"]["responses"][200]["content"]["application/json"];
 /** `GET /api/v1/servers/{serverId}/web-checks/{checkId}` 成功时的响应体。 */

package/dist/monitoring/v1/schema.d.ts

@@ -958,6 +958,10 @@ export interface components {
         Error: {
             code?: string;
             message: string;
+            /**
+             * @description What a given `code` carries alongside the message. The keys depend on the code,
+             *     and a client that does not recognise one ignores it.
+             */
             meta?: {
                 [key: string]: unknown;
             };

package/dist/notification/v1/schema.d.ts

@@ -624,6 +624,10 @@ export interface components {
         Error: {
             code?: string;
             message: string;
+            /**
+             * @description What a given `code` carries alongside the message. The keys depend on the code,
+             *     and a client that does not recognise one ignores it.
+             */
             meta?: {
                 [key: string]: unknown;
             };

package/dist/support/v1/schema.d.ts

@@ -298,6 +298,10 @@ export interface components {
         Error: {
             code?: string;
             message: string;
+            /**
+             * @description What a given `code` carries alongside the message. The keys depend on the code,
+             *     and a client that does not recognise one ignores it.
+             */
             meta?: {
                 [key: string]: unknown;
             };

package/dist/tunnel/v1/schema.d.ts

@@ -11,20 +11,20 @@ export interface paths {
             cookie?: never;
         };
         /**
-         * 查看本项目的四层隧道
-         * @description 还没生成过时返回 `TUNNEL_NOT_FOUND`——首屏据此决定画「生成订阅链接」那个按钮还是画结果。
+         * Get the layer 4 tunnel of the current project
+         * @description `TUNNEL_NOT_FOUND` means no tunnel has been generated yet.
          *
-         *     项目未获开放时返回 403 `TUNNEL_NOT_ENTITLED`，那是另一件事：控制台据此把四层隧道的入口整个收起来，而不是画那个按钮。
+         *     403 `TUNNEL_NOT_ENTITLED` states something else: the project has not been entitled to layer 4 at all.
          *
-         *     订阅地址、用量、配额各有自己的接口，这里不重复返回。
+         *     The subscription address, the usage and the quota each have their own endpoint and are not repeated here.
          */
         get: operations["get-l4-tunnel"];
         put?: never;
         /**
-         * 生成四层隧道
-         * @description **幂等**：已经有了再调一次返回同一条，不报错。按钮被点两次是安全的。
+         * Generate the layer 4 tunnel
+         * @description **Idempotent**: calling it again returns the existing tunnel rather than an error.
          *
-         *     生成之后请调订阅接口取地址，本接口不返回它。
+         *     Read the address from the subscription endpoint afterwards; it is not returned here.
          */
         post: operations["generate-l4-tunnel"];
         delete?: never;
@@ -41,12 +41,12 @@ export interface paths {
             cookie?: never;
         };
         /**
-         * 获取订阅地址
-         * @description **这条 URL 是凭据，等同于密码。** 拿着它就能取到这个项目的全部节点和密码，所以它只在这一个接口里出现，一次一条——不进任何列表，也不在隧道详情里。
+         * Get the subscription address
+         * @description **This URL is a credential, equivalent to a password.** It yields every node of the project along with their passwords. It is returned here alone, and appears neither in the tunnel itself nor in any list.
          *
-         *     客户端不应在用户主动请求之前调用它：这个接口的每一次调用都会被记进操作日志。
+         *     Do not call this endpoint before the user asks for the address.
          *
-         *     `status` 为 `preparing` 时链接**照样有效**，内容会在拉取那一刻重新派生。它只该影响页面上说什么。
+         *     A `status` of `preparing` leaves the link usable; its contents are derived at the moment it is fetched.
          */
         get: operations["get-l4-tunnel-subscription"];
         put?: never;
@@ -67,14 +67,14 @@ export interface paths {
         get?: never;
         put?: never;
         /**
-         * 重置订阅地址与节点密码
-         * @description **这是凭据泄露时的处置手段，会让已分发出去的每一份订阅立即失效。**
+         * Rotate the subscription address and the node passwords
+         * @description **This is the remedy for an exposed credential, and every subscription already distributed stops working at once.**
          *
-         *     订阅 token 和节点密码同时更换，所有客户端都必须重新拉取一次订阅才能继续使用。调用前请确认这确实是想要的结果。
+         *     The subscription token and the node passwords are replaced together, so every client has to fetch the subscription again before it can carry on. Confirm that this is the intended outcome before calling.
          *
-         *     隧道被平台停用时无法重置（`TUNNEL_DISABLED_FOR_ROTATE`），需要先处理停用的原因。
+         *     A tunnel disabled by the platform cannot be rotated (`TUNNEL_DISABLED_FOR_ROTATE`); resolve the cause first.
          *
-         *     重置后请调订阅接口取新地址，**本接口不返回它**。
+         *     Read the new address from the subscription endpoint afterwards; **it is not returned here**.
          */
         post: operations["rotate-l4-tunnel-subscription"];
         delete?: never;
@@ -91,10 +91,10 @@ export interface paths {
             cookie?: never;
         };
         /**
-         * 查看本期用量
-         * @description 实时查询，不经过缓存。
+         * Get the usage of the current period
+         * @description Read live.
          *
-         *     判断是否超额只看 `billed_bytes`：线路可以设置倍率（如 1.5× 或 0×），`raw_bytes` 是实际传输量，两者不一定相等。`quota_bytes` 为 0 表示不限量。
+         *     Only `billed_bytes` decides whether the quota is exceeded: a route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
          */
         get: operations["get-l4-tunnel-usage"];
         put?: never;
@@ -113,10 +113,10 @@ export interface paths {
             cookie?: never;
         };
         /**
-         * 查看按天用量
-         * @description 按自然日切分。没有流量的日子不会出现在结果里（不补零），画图那一侧要自己补齐日期轴——否则一段没人用的日子会被画成一条直接连过去的线，看起来像那几天一直在匀速跑流量。
+         * Get daily usage
+         * @description Cut by calendar day. A day carrying no traffic is absent rather than zero, so a chart has to fill the date axis itself.
          *
-         *     把这里的天加起来**不等于**本期用量，这是有意的：本期按计费周期切，而且「重置本期用量」只作用于本期，日汇总一行都不删。
+         *     These days do not sum to the usage of the current period, which is cut by billing period. Resetting the usage of the current period leaves every daily total in place.
          */
         get: operations["list-l4-tunnel-usage-series"];
         put?: never;
@@ -134,6 +134,10 @@ export interface components {
         Error: {
             code?: string;
             message: string;
+            /**
+             * @description What a given `code` carries alongside the message. The keys depend on the code,
+             *     and a client that does not recognise one ignores it.
+             */
             meta?: {
                 [key: string]: unknown;
             };
@@ -142,22 +146,22 @@ export interface components {
         };
         SubscriptionResource: {
             /**
-             * @description ready 表示节点已全部下发；preparing 表示仍在下发——此时链接照样可用
+             * @description ready means every node has been distributed; preparing means distribution is still under way, and the link works either way
              * @enum {string}
              */
             status: "preparing" | "ready";
             /** Format: date-time */
             updated_at: string;
-            /** @description 订阅地址。这是一条长期有效的凭据，等同于密码，请勿转发或截图分享 */
+            /** @description The subscription address. It is a long-lived credential equivalent to a password; do not forward it or share a screenshot of it */
             url: string;
             /** Format: int64 */
             version: number;
         };
-        /** @description 当前项目那条四层隧道。它只回答一个问题：生成过没有。 */
+        /** @description The layer 4 tunnel of the current project. It answers a single question — whether the tunnel has been generated */
         TunnelResource: {
             /** Format: date-time */
             created_at: string;
-            /** @description 隧道当前是否可用。为 false 表示被平台停用（欠费、违规或项目停服），需要先处理停用的原因 */
+            /** @description Whether the tunnel is currently usable. false means the platform has disabled it — for an unpaid balance, a violation, or a suspended project — and the cause has to be resolved first */
             enabled: boolean;
             /** Format: uuid */
             id: string;
@@ -173,41 +177,41 @@ export interface components {
         UsageResource: {
             /**
              * Format: int64
-             * @description 按线路倍率折算后的用量，配额比对以此为准
+             * @description Usage after the multiplier of each route has been applied. Quota is measured against this value
              */
             billed_bytes: number;
             over_quota: boolean;
-            /** @description 本期计费周期的结束日（YYYY-MM-DD） */
+            /** @description Last day of the current billing period (YYYY-MM-DD) */
             period_end: string;
-            /** @description 本期计费周期的起始日（YYYY-MM-DD） */
+            /** @description First day of the current billing period (YYYY-MM-DD) */
             period_start: string;
             /**
              * Format: int64
-             * @description 上游给出的真实配额，0 表示不限量
+             * @description The quota in force; 0 means unlimited
              */
             quota_bytes: number;
             /**
              * Format: date-time
-             * @description 上游判定超额的时刻；null 表示未超额
+             * @description When the quota was found to be exceeded; null while it has not been
              */
             quota_exceeded_at: string | null;
             /**
              * Format: int64
-             * @description 实际传输的字节，不用于配额比对
+             * @description Bytes actually transferred. Quota is not measured against this value
              */
             raw_bytes: number;
             /** Format: int64 */
             upload_bytes: number;
             /**
              * Format: double
-             * @description 上游给出的用量百分比
+             * @description Usage as a percentage of the quota
              */
             usage_percent: number;
         };
         UsageSeriesResource: {
             /**
              * Format: int64
-             * @description 上游实际采用的天数，可能被它夹到 1–365
+             * @description The number of days actually covered, which may have been clamped to the range 1–365
              */
             days: number;
             points: components["schemas"]["UsageDayResource"][];
@@ -369,7 +373,7 @@ export interface operations {
     "list-l4-tunnel-usage-series": {
         parameters: {
             query?: {
-                /** @description 取最近多少天。0 表示用上游的默认值（30）——上游只接受 1–365，超出会被它夹住 */
+                /** @description How many days to cover. 0 requests the default of 30; the range accepted is 1–365, and a larger value is clamped to it */
                 days?: number;
             };
             header?: never;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leaflow/sdk",
-  "version": "0.54.3",
+  "version": "0.55.0",
   "description": "Leaflow 平台 API 的 TypeScript SDK",
   "license": "MIT",
   "repository": {