@leaflow/sdk 0.0.0-dev.510.g8eb7f2e → 0.0.0-dev.516.g28eeab9

package/dist/proto/leaflow/fleet/virtualdesktop/datatransfer/v1/datatransfer_pb.d.ts

@@ -8,6 +8,42 @@ import type { Message } from "@bufbuild/protobuf";
  */
 export declare const file_leaflow_fleet_virtualdesktop_datatransfer_v1_datatransfer: GenFile;
 /**
+ * Windows 原生表示不能仅按格式名合并：同一格式的 aspect、index 和介质各自独立。
+ * 无法用标准媒体类型完整表达的可序列化表示使用下列媒体类型（参数均为 ASCII）：
+ * application/x-leaflow-windows-format;name=<utf16hex>;aspect=<u32>;index=<i32>;medium=<kind>
+ * name 为格式名每个 UTF-16 单元的四位十六进制串，不含终止 NUL；接收端以名称重新
+ * 注册格式，不得跨机复用来源的注册号。非注册格式改用 id=<1..49151>，不得同时带 name。
+ * aspect、index、medium 必须显式存在，不得丢失、重复或以未知参数降级为其它格式。
+ * medium=bytes 为 HGLOBAL/IStream 的可序列化字节，medium=storage 为完整 Compound File
+ * Binary 表示，medium=emf 为 TYMED_ENHMF 的完整增强型图元文件记录，不得降为位图。
+ * 普通 CF_ENHMETAFILE 的内容表示使用 image/emf；其它 aspect/index 保留显式选择器。
+ * medium=file 为 TYMED_FILE 承载的某种格式的完整正文，不是 lpszFileName 或文件引用。
+ * 仅在读取该表示时打开来源本机介质，按块取得正文；空正文有效，读取失败不改用其它格式。
+ * 接收端按需创建独立的本机临时介质文件，文件名仅交给本机 OLE 目标，绝不跨机发送。
+ * 已交出的介质由自己的 STGMEDIUM/pUnkForRelease 持有，不随原声明或读取期结束提前删除；
+ * 最后一个介质引用释放时删除自己创建的临时文件。来源介质仍按原 STGMEDIUM 的规则释放。
+ * medium=metafile-picture 为 TYMED_MFPICT：先依次编码 mm、xExt、yExt 三个 i32 小端数，
+ * 随后是完整 WMF 记录；不得发送 METAFILEPICT 的本机结构、对齐填充或 hMF 句柄。
+ * medium=gdi 为 TYMED_GDI：先编码对象种类 u32 小端数，7 为位图，5 为调色板。
+ * 位图随后为 40 字节 BITMAPINFOHEADER、BI_BITFIELDS 所需的三个颜色掩码、声明的
+ * RGBQUAD 颜色表及 DWORD 对齐的完整像素行；仅使用 BI_RGB 或 BI_BITFIELDS，保留
+ * 有效色深和像素，biSizeImage 精确等于像素长度，不含 BMP 文件头或本机指针。
+ * 调色板随后为 LOGPALETTE：version=0x300、条目数两个 u16 小端数，再依次编码每个
+ * PALETTEENTRY 的 red、green、blue、flags 四字节，接收端创建新的本机 GDI 对象。
+ * FORMATETC 的非空 ptd 另以可选 device=<bytehex> 参数声明整个 DVTARGETDEVICE；
+ * 每字节两个十六进制字符，包含 tdSize 指定的完整描述、DEVMODE 和驱动私有尾部。
+ * 省略 device 表示空 ptd；长度和内部偏移必须有效，不得把畸形或重复参数降级为普通
+ * 注册格式。设备描述也是表示身份，枚举、读取、缓存和重建不得合并不同 device。
+ * 各次原生枚举交出独立、可由 COM 分配器释放的副本；不得预读正文来取得该声明。
+ * 设备描述仅供保留和匹配，不得据此加载来源驱动或创建来源设备，也不进入日志。
+ * 本机介质与以完整媒体类型名提供的原始 HGLOBAL/IStream 字节表示可同时存在；
+ * 两者声明同一跨机格式时优先读取原始序列化字节，不得先经过本机 GDI 编组而改变
+ * 像素、色表、掩码或其它记录。两种本机表示共用同一媒体类型、读取期和数据通道。
+ * 接收端从记录重建介质，绝不把原生句柄、指针、COM 接口或源文件路径当正文。
+ * CF_HDROP(id=15)、FileContents、FileGroupDescriptor、PIDL、FileName 等文件/路径格式及
+ * 拖放控制格式仍归 filetransfer 或拖放适配，不得用此媒体类型绕过文件引用和权限。
+ * 原生声明和取得流引用不能预读正文；各表示继续独立按需读取、校验和取消。
+ *
  * Data of one format.
  *
  * @generated from message leaflow.fleet.virtualdesktop.datatransfer.v1.DataTransferItem
@@ -1364,7 +1400,8 @@ export type DragPolicy = Message<"leaflow.fleet.virtualdesktop.datatransfer.v1.D
      */
     allowedMimeTypes: string[];
     /**
-     * The longest a drag may last, at most 5 minutes. Unset or 0: no drags.
+     * DragDrop 之前物理手势的最长时间，至多 5 分钟；未设置或 0 表示不能拖拽。
+     * 已受理的原生确认、格式读取及文件交付不受旧手势时限约束，不代表放宽当前权限。
      *
      * @generated from field: google.protobuf.Duration max_duration = 4;
      */

package/dist/routes.d.ts

@@ -142,6 +142,38 @@ export declare const routes: readonly [{
     readonly operationId: "revoke-ssh-key";
     readonly securityScheme: "AccessToken";
     readonly upstreamUrl: "https://account.leaflow.cloud";
+}, {
+    readonly service: "account";
+    readonly contract: "account";
+    readonly method: "GET";
+    readonly path: "/account/v1/applications/{clientId}";
+    readonly operationId: "get-application";
+    readonly securityScheme: "AccessToken";
+    readonly upstreamUrl: "https://account.leaflow.cloud";
+}, {
+    readonly service: "account";
+    readonly contract: "account";
+    readonly method: "GET";
+    readonly path: "/account/v1/me/authorized-applications";
+    readonly operationId: "list-authorized-applications";
+    readonly securityScheme: "AccessToken";
+    readonly upstreamUrl: "https://account.leaflow.cloud";
+}, {
+    readonly service: "account";
+    readonly contract: "account";
+    readonly method: "POST";
+    readonly path: "/account/v1/me/authorized-applications";
+    readonly operationId: "authorize-application";
+    readonly securityScheme: "AccessToken";
+    readonly upstreamUrl: "https://account.leaflow.cloud";
+}, {
+    readonly service: "account";
+    readonly contract: "account";
+    readonly method: "DELETE";
+    readonly path: "/account/v1/me/authorized-applications/{authorizationId}";
+    readonly operationId: "revoke-authorized-application";
+    readonly securityScheme: "AccessToken";
+    readonly upstreamUrl: "https://account.leaflow.cloud";
 }, {
     readonly service: "account";
     readonly contract: "account";

package/dist/routes.js

@@ -162,6 +162,42 @@ export const routes = [
         securityScheme: "AccessToken",
         upstreamUrl: "https://account.leaflow.cloud",
     },
+    {
+        service: "account",
+        contract: "account",
+        method: "GET",
+        path: "/account/v1/applications/{clientId}",
+        operationId: "get-application",
+        securityScheme: "AccessToken",
+        upstreamUrl: "https://account.leaflow.cloud",
+    },
+    {
+        service: "account",
+        contract: "account",
+        method: "GET",
+        path: "/account/v1/me/authorized-applications",
+        operationId: "list-authorized-applications",
+        securityScheme: "AccessToken",
+        upstreamUrl: "https://account.leaflow.cloud",
+    },
+    {
+        service: "account",
+        contract: "account",
+        method: "POST",
+        path: "/account/v1/me/authorized-applications",
+        operationId: "authorize-application",
+        securityScheme: "AccessToken",
+        upstreamUrl: "https://account.leaflow.cloud",
+    },
+    {
+        service: "account",
+        contract: "account",
+        method: "DELETE",
+        path: "/account/v1/me/authorized-applications/{authorizationId}",
+        operationId: "revoke-authorized-application",
+        securityScheme: "AccessToken",
+        upstreamUrl: "https://account.leaflow.cloud",
+    },
     {
         service: "account",
         contract: "account",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leaflow/sdk",
-  "version": "0.0.0-dev.510.g8eb7f2e",
+  "version": "0.0.0-dev.516.g28eeab9",
   "description": "Leaflow 平台 API 的 TypeScript SDK",
   "license": "MIT",
   "repository": {

package/dist/compute/v2/generated/validators/rescueInstanceRequestBody.zod.d.ts

@@ -1,42 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Compute API
- * Leaflow Compute user API for managing instances, volumes, snapshots, volume backups, public and private images, virtual private clouds, subnets, routes, security groups, network interfaces and elastic IPs.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `scopedTokenAuth` security scheme. The catalog reads, which list and retrieve regions, availability zones, instance types, volume types, public images and elastic IP lines, also answer without a token, so a visitor can configure a purchase and price it with Billing before signing in. A token given to them is still verified, and an invalid one is refused.
- *
- * ## Conventions
- *
- * - **Purchases.** A purchase that creates resources returns them together with the `checkout_session_id` of its Billing Checkout Session and, once checkout completes, its `order_id`. They are readable at once and start as `pending`: checkout may not be complete, the order has not been accepted, nothing exists in the cloud, no inventory such as an address is held, and fields known only after allocation, such as addresses, are null. Once Billing accepts the order, the resource is created: it stays `pending`, then reaches its usual status, such as `running` or `available`. When the Checkout Session expires, the order is declined, canceled or expires, or creation fails, the resource ends `failed` and `failure_reason` states why; the charge for a resource that failed after acceptance is refunded. A purchased change, such as a resize requested with `instance_type_id`, `size_gib` or `bandwidth_mbps` on the resource, returns the resource unchanged with the Checkout Session for the change, and applies once its order is accepted.
- * - **Commercial terms.** Compute catalogs describe technical specifications and, for each order line a purchase makes, how it is sold in Billing (a `BillingComponent`: its Plan, dimensions, what its quantity counts and what its meters read); prices, amounts and currency belong to Billing. A purchase chooses its terms with `billing`, and Billing selects the matching price. Read prices and their rates with Billing's `search-prices` from those components, quote a proposed purchase with `get-quote`, and a change of a resource by its `subscription_id`; Compute has no quote or price proxy endpoint and returns no amounts.
- * - **Checkout.** `checkout` is passed to Billing unchanged. Omit it for automatic checkout, which completes checkout within the request and pays from eligible credit grants and balance; insufficient funds refuse the request with HTTP 422 `BILLING_INSUFFICIENT_FUNDS`, and nothing is created. With `checkout.mode` set to `deferred`, the resources are returned `pending` with an open Checkout Session and no order, even for a zero total; nothing is created until the customer completes checkout in Billing, where a promotion code can be applied, and the order is paid. Do not submit the purchase again after paying; after an uncertain response, look the Checkout Session up in Billing first.
- * - **Quotas.** A creation, purchase or resize that adds to what a project holds in a region is checked against the project's quota there before anything is ordered or created, and is refused with HTTP 409 `COMPUTE_PROJECT_QUOTA_EXCEEDED`, whose `meta` names the `resource`, its `limit`, the amount `used` and the amount `requested`. An instance purchase counts the volumes, the new primary network interface and the new elastic IP bought with each instance. Read the limits with `list-quotas`; a limit no operator set is the platform default.
- * - **Projects.** Resource ownership and project identifiers refer to IAM platform projects, not OpenStack tenants. Instances, images and networks share one infrastructure OpenStack project; the platform project remains the authorization and ownership boundary.
- * - **Custom methods.** An action that is not one of the standard methods (list, get, create, update, delete) is a custom method, `POST` on the resource's path followed by `:` and the verb, as in `POST /api/v2/instances/{id}:reboot` (AIP-136). A state is changed by its custom method, never by writing the state: `:start` and `:stop`, `:rescue` and `:unrescue`, `:associate` and `:disassociate`.
- * - **Operations.** Requests such as `:start`, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `status` names it, as in `starting` or `deleting`; once it has finished the resource shows its new status and the result. A resource with an operation in progress refuses another operation with HTTP 409 `COMPUTE_RESOURCE_BUSY`; an operation involving two resources, such as attaching a volume, is refused when either has one. A purchased change, such as a resize, is an operation from the moment its Checkout Session is created until the change is applied, the session expires or its order is canceled. Renaming and replacing labels or notes are not operations and are accepted at any time. **Updating.** A `PATCH` carries only mutable fields, all optional and at least one given, and answers 200 when only descriptive fields changed and 202 when an operation started. An operational field (`instance_type_id`, `size_gib`, `bandwidth_mbps`) cannot be combined with any other field in the same request: it is refused with 422 `UPDATE_FIELDS_COMBINED`, because a rename that committed beside a change that was then refused would leave the request half applied.
- * - **Billing relationships.** A purchased resource records its `checkout_session_id` and, once checkout completes, its `order_id`, `order_item_id` and `subscription_id`. Its `access_state` is `pending` until the order is accepted and delivery settles it, then `enabled`; a subscription that lapses suspends or reclaims the resource it pays for. Deleting a resource that subscriptions pay for cancels the subscriptions of its `release_set` in Billing, and the deletion answers with that cancellation.
- * - **Availability zones.** A volume and an instance must reside in the same availability zone to be attached. An instance type and a volume type each belong to one availability zone, as on GCP, so a purchase names the type and the type names the zone; the volumes bought with an instance have to be of types of the instance type's zone.
- * - **IPv6 is routed, not translated.** A virtual private cloud with IPv6 holds a /56 and each of its subnets a /64 of it, as on Alibaba Cloud, Tencent Cloud and Azure; IPv6 and its security groups require no EIP or NAT gateway. EIP and NATGateway are IPv4 products; IPv6 EIP, NAT66 and IPv6 port forwarding are not supported.
- * - **Elastic IP release.** A released address returns to available inventory as soon as its cleanup is confirmed, with no cooldown period. Removing or replacing an elastic IP's association keeps the address held by the project and does not release it.
- * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
- *
- * ## Resource identifiers
- *
- * Compute resource IDs use the fixed TypeID prefix declared in their schema. UUID text is not accepted for these resource IDs. Project, order, subscription and Billing Plan identifiers remain UUIDs. Historical operation-log subject IDs are audit facts and are not rewritten.
- *
- * ## Error meta
- *
- * Resource identifiers in an error's `meta` (`resource_id`, `volume_id`, `network_interface_id` and the like) are TypeIDs, in the same form as the identifiers in resources. `meta.resource_type` is the resource's name as written in paths, with underscores: `instance`, `volume`, `elastic_ip`, `network_interface`, `virtual_private_cloud`, `private_image`, `volume_backup`, and so on.
- * OpenAPI spec version: 2.0.0
- */
-import * as zod from "zod";
-export declare const rescueInstanceRequestBodyPasswordMin = 12;
-export declare const rescueInstanceRequestBodyPasswordMax = 128;
-export declare const RescueInstanceRequestBody: zod.ZodObject<{
-    password: zod.ZodString;
-}, zod.z.core.$strict>;
-export type RescueInstanceRequestBody = zod.input<typeof RescueInstanceRequestBody>;
-export type RescueInstanceRequestBodyOutput = zod.output<typeof RescueInstanceRequestBody>;

package/dist/compute/v2/generated/validators/rescueInstanceRequestBody.zod.js

@@ -1,44 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Compute API
- * Leaflow Compute user API for managing instances, volumes, snapshots, volume backups, public and private images, virtual private clouds, subnets, routes, security groups, network interfaces and elastic IPs.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `scopedTokenAuth` security scheme. The catalog reads, which list and retrieve regions, availability zones, instance types, volume types, public images and elastic IP lines, also answer without a token, so a visitor can configure a purchase and price it with Billing before signing in. A token given to them is still verified, and an invalid one is refused.
- *
- * ## Conventions
- *
- * - **Purchases.** A purchase that creates resources returns them together with the `checkout_session_id` of its Billing Checkout Session and, once checkout completes, its `order_id`. They are readable at once and start as `pending`: checkout may not be complete, the order has not been accepted, nothing exists in the cloud, no inventory such as an address is held, and fields known only after allocation, such as addresses, are null. Once Billing accepts the order, the resource is created: it stays `pending`, then reaches its usual status, such as `running` or `available`. When the Checkout Session expires, the order is declined, canceled or expires, or creation fails, the resource ends `failed` and `failure_reason` states why; the charge for a resource that failed after acceptance is refunded. A purchased change, such as a resize requested with `instance_type_id`, `size_gib` or `bandwidth_mbps` on the resource, returns the resource unchanged with the Checkout Session for the change, and applies once its order is accepted.
- * - **Commercial terms.** Compute catalogs describe technical specifications and, for each order line a purchase makes, how it is sold in Billing (a `BillingComponent`: its Plan, dimensions, what its quantity counts and what its meters read); prices, amounts and currency belong to Billing. A purchase chooses its terms with `billing`, and Billing selects the matching price. Read prices and their rates with Billing's `search-prices` from those components, quote a proposed purchase with `get-quote`, and a change of a resource by its `subscription_id`; Compute has no quote or price proxy endpoint and returns no amounts.
- * - **Checkout.** `checkout` is passed to Billing unchanged. Omit it for automatic checkout, which completes checkout within the request and pays from eligible credit grants and balance; insufficient funds refuse the request with HTTP 422 `BILLING_INSUFFICIENT_FUNDS`, and nothing is created. With `checkout.mode` set to `deferred`, the resources are returned `pending` with an open Checkout Session and no order, even for a zero total; nothing is created until the customer completes checkout in Billing, where a promotion code can be applied, and the order is paid. Do not submit the purchase again after paying; after an uncertain response, look the Checkout Session up in Billing first.
- * - **Quotas.** A creation, purchase or resize that adds to what a project holds in a region is checked against the project's quota there before anything is ordered or created, and is refused with HTTP 409 `COMPUTE_PROJECT_QUOTA_EXCEEDED`, whose `meta` names the `resource`, its `limit`, the amount `used` and the amount `requested`. An instance purchase counts the volumes, the new primary network interface and the new elastic IP bought with each instance. Read the limits with `list-quotas`; a limit no operator set is the platform default.
- * - **Projects.** Resource ownership and project identifiers refer to IAM platform projects, not OpenStack tenants. Instances, images and networks share one infrastructure OpenStack project; the platform project remains the authorization and ownership boundary.
- * - **Custom methods.** An action that is not one of the standard methods (list, get, create, update, delete) is a custom method, `POST` on the resource's path followed by `:` and the verb, as in `POST /api/v2/instances/{id}:reboot` (AIP-136). A state is changed by its custom method, never by writing the state: `:start` and `:stop`, `:rescue` and `:unrescue`, `:associate` and `:disassociate`.
- * - **Operations.** Requests such as `:start`, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `status` names it, as in `starting` or `deleting`; once it has finished the resource shows its new status and the result. A resource with an operation in progress refuses another operation with HTTP 409 `COMPUTE_RESOURCE_BUSY`; an operation involving two resources, such as attaching a volume, is refused when either has one. A purchased change, such as a resize, is an operation from the moment its Checkout Session is created until the change is applied, the session expires or its order is canceled. Renaming and replacing labels or notes are not operations and are accepted at any time. **Updating.** A `PATCH` carries only mutable fields, all optional and at least one given, and answers 200 when only descriptive fields changed and 202 when an operation started. An operational field (`instance_type_id`, `size_gib`, `bandwidth_mbps`) cannot be combined with any other field in the same request: it is refused with 422 `UPDATE_FIELDS_COMBINED`, because a rename that committed beside a change that was then refused would leave the request half applied.
- * - **Billing relationships.** A purchased resource records its `checkout_session_id` and, once checkout completes, its `order_id`, `order_item_id` and `subscription_id`. Its `access_state` is `pending` until the order is accepted and delivery settles it, then `enabled`; a subscription that lapses suspends or reclaims the resource it pays for. Deleting a resource that subscriptions pay for cancels the subscriptions of its `release_set` in Billing, and the deletion answers with that cancellation.
- * - **Availability zones.** A volume and an instance must reside in the same availability zone to be attached. An instance type and a volume type each belong to one availability zone, as on GCP, so a purchase names the type and the type names the zone; the volumes bought with an instance have to be of types of the instance type's zone.
- * - **IPv6 is routed, not translated.** A virtual private cloud with IPv6 holds a /56 and each of its subnets a /64 of it, as on Alibaba Cloud, Tencent Cloud and Azure; IPv6 and its security groups require no EIP or NAT gateway. EIP and NATGateway are IPv4 products; IPv6 EIP, NAT66 and IPv6 port forwarding are not supported.
- * - **Elastic IP release.** A released address returns to available inventory as soon as its cleanup is confirmed, with no cooldown period. Removing or replacing an elastic IP's association keeps the address held by the project and does not release it.
- * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
- *
- * ## Resource identifiers
- *
- * Compute resource IDs use the fixed TypeID prefix declared in their schema. UUID text is not accepted for these resource IDs. Project, order, subscription and Billing Plan identifiers remain UUIDs. Historical operation-log subject IDs are audit facts and are not rewritten.
- *
- * ## Error meta
- *
- * Resource identifiers in an error's `meta` (`resource_id`, `volume_id`, `network_interface_id` and the like) are TypeIDs, in the same form as the identifiers in resources. `meta.resource_type` is the resource's name as written in paths, with underscores: `instance`, `volume`, `elastic_ip`, `network_interface`, `virtual_private_cloud`, `private_image`, `volume_backup`, and so on.
- * OpenAPI spec version: 2.0.0
- */
-import * as zod from "zod";
-export const rescueInstanceRequestBodyPasswordMin = 12;
-export const rescueInstanceRequestBodyPasswordMax = 128;
-export const RescueInstanceRequestBody = zod.strictObject({
-    password: zod
-        .string()
-        .min(rescueInstanceRequestBodyPasswordMin)
-        .max(rescueInstanceRequestBodyPasswordMax)
-        .describe("Password for the rescue environment. Generate and retain a strong password before calling."),
-});