@leaflow/sdk 0.0.0-dev.113.g5d6fb99

package/dist/monitoring/v1/schema.js

@@ -0,0 +1,5 @@
+/**
+ * This file was auto-generated by openapi-typescript.
+ * Do not make direct changes to the file.
+ */
+export {};

package/dist/src/client.d.ts

@@ -0,0 +1,57 @@
+import type { paths as AccountPaths } from "../gen/account/v1/schema.js";
+import type { paths as AssistantPaths } from "../gen/assistant/v1/schema.js";
+import type { paths as CanopyPaths } from "../gen/canopy/v1/schema.js";
+import type { paths as ComputePaths } from "../gen/compute/v1/schema.js";
+import type { paths as IamPaths } from "../gen/iam/v1/schema.js";
+import type { paths as MonitoringPaths } from "../gen/monitoring/v1/schema.js";
+import type { paths as TunnelPaths } from "../gen/tunnel/v1/schema.js";
+/**
+ * 令牌怎么拿到。
+ *
+ * 是个函数而不是一个字符串：项目令牌会过期，而它没有刷新接口——过期之后要拿账号令牌重新换一张
+ * （见 account.exchangeProjectToken）。传字符串的话，那次续期要调用方自己想起来重建整个
+ * 客户端，而忘了的表现是「用着用着就全是 401」。
+ */
+export type TokenSource = string | (() => string | Promise<string>);
+export interface ClientOptions {
+    /** 网关地址，比如 https://api.leaflow.net */
+    baseUrl: string;
+    /**
+     * 项目令牌。它同时说明当前用户和当前项目，所以**这里不传 projectId**——
+     * 当前项目由令牌断言，接口路径上也没有这个参数。要换项目就换一张令牌。
+     */
+    token: TokenSource;
+    fetch?: typeof globalThis.fetch;
+}
+/**
+ * 账号 API 用的是**另一张令牌**，所以它有自己的入口。
+ *
+ * 账号令牌来自 auth.leaflow.net 的登录，只说明你是谁、不带任何项目；项目令牌是拿它去 IAM
+ * 换的。两者混用的表现是 401，而错误信息说不清是哪一张不对——分成两个入口之后，调用方在写
+ * 代码那一刻就得选对。
+ */
+export interface AccountClientOptions {
+    baseUrl: string;
+    /** 账号令牌 */
+    token: TokenSource;
+    fetch?: typeof globalThis.fetch;
+}
+/**
+ * 一个项目令牌，七个服务。
+ *
+ * 每个服务是一个独立的客户端，各自认自己那份 schema —— 类型不跨服务共享。这不是为了整齐：
+ * compute 和 tunnel 各有一个 OperationLogResource，它们是两个不同的类型，合进一个命名空间
+ * 之后先声明的那个会盖掉另一个，而盖掉不报错。
+ */
+export declare function createClient(options: ClientOptions): {
+    assistant: import("openapi-fetch").Client<AssistantPaths, `${string}/${string}`>;
+    canopy: import("openapi-fetch").Client<CanopyPaths, `${string}/${string}`>;
+    compute: import("openapi-fetch").Client<ComputePaths, `${string}/${string}`>;
+    iam: import("openapi-fetch").Client<IamPaths, `${string}/${string}`>;
+    monitoring: import("openapi-fetch").Client<MonitoringPaths, `${string}/${string}`>;
+    tunnel: import("openapi-fetch").Client<TunnelPaths, `${string}/${string}`>;
+};
+/** 账号 API：注册、账号本身、我参与了哪些项目、换取项目令牌。 */
+export declare function createAccountClient(options: AccountClientOptions): import("openapi-fetch").Client<AccountPaths, `${string}/${string}`>;
+export type LeaflowClient = ReturnType<typeof createClient>;
+export type AccountClient = ReturnType<typeof createAccountClient>;

package/dist/src/client.js

@@ -0,0 +1,41 @@
+import createFetchClient, {} from "openapi-fetch";
+async function resolveToken(source) {
+    return typeof source === "string" ? source : await source();
+}
+function authorization(source) {
+    return {
+        async onRequest({ request }) {
+            request.headers.set("Authorization", `Bearer ${await resolveToken(source)}`);
+            return request;
+        },
+    };
+}
+function build(options) {
+    const client = createFetchClient({
+        baseUrl: options.baseUrl,
+        fetch: options.fetch,
+    });
+    client.use(authorization(options.token));
+    return client;
+}
+/**
+ * 一个项目令牌，七个服务。
+ *
+ * 每个服务是一个独立的客户端，各自认自己那份 schema —— 类型不跨服务共享。这不是为了整齐：
+ * compute 和 tunnel 各有一个 OperationLogResource，它们是两个不同的类型，合进一个命名空间
+ * 之后先声明的那个会盖掉另一个，而盖掉不报错。
+ */
+export function createClient(options) {
+    return {
+        assistant: build(options),
+        canopy: build(options),
+        compute: build(options),
+        iam: build(options),
+        monitoring: build(options),
+        tunnel: build(options),
+    };
+}
+/** 账号 API：注册、账号本身、我参与了哪些项目、换取项目令牌。 */
+export function createAccountClient(options) {
+    return build(options);
+}

package/dist/src/index.d.ts

@@ -0,0 +1,9 @@
+export { createClient, createAccountClient } from "./client.js";
+export type { AccountClient, AccountClientOptions, ClientOptions, LeaflowClient, TokenSource, } from "./client.js";
+export type { paths as AccountPaths, components as AccountTypes } from "../gen/account/v1/schema.js";
+export type { paths as AssistantPaths, components as AssistantTypes } from "../gen/assistant/v1/schema.js";
+export type { paths as CanopyPaths, components as CanopyTypes } from "../gen/canopy/v1/schema.js";
+export type { paths as ComputePaths, components as ComputeTypes } from "../gen/compute/v1/schema.js";
+export type { paths as IamPaths, components as IamTypes } from "../gen/iam/v1/schema.js";
+export type { paths as MonitoringPaths, components as MonitoringTypes } from "../gen/monitoring/v1/schema.js";
+export type { paths as TunnelPaths, components as TunnelTypes } from "../gen/tunnel/v1/schema.js";

package/dist/src/index.js

@@ -0,0 +1 @@
+export { createClient, createAccountClient } from "./client.js";

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

@@ -0,0 +1,34 @@
+export type { paths, components, operations, webhooks } from "./schema.js";
+import type { operations } from "./schema.js";
+/** `GET /api/v1/operation-logs` 成功时的响应体。 */
+export type ListTunnelOperationLogsResult = operations["list-tunnel-operation-logs"]["responses"][200]["content"]["application/json"];
+/** `GET /api/v1/plans` 成功时的响应体。 */
+export type ListTunnelPlansResult = operations["list-tunnel-plans"]["responses"][200]["content"]["application/json"];
+/** `DELETE /api/v1/tunnel` 成功时的响应体。 */
+export type CloseTunnelResult = operations["close-tunnel"]["responses"][200]["content"]["application/json"];
+/** `GET /api/v1/tunnel` 成功时的响应体。 */
+export type GetTunnelResult = operations["get-tunnel"]["responses"][200]["content"]["application/json"];
+/** `PATCH /api/v1/tunnel` 成功时的响应体。 */
+export type UpdateTunnelProfileResult = operations["update-tunnel-profile"]["responses"][200]["content"]["application/json"];
+/** `PATCH /api/v1/tunnel` 的请求体。 */
+export type UpdateTunnelProfileBody = NonNullable<operations["update-tunnel-profile"]["requestBody"]>["content"]["application/json"];
+/** `POST /api/v1/tunnel` 成功时的响应体。 */
+export type OpenTunnelResult = operations["open-tunnel"]["responses"][201]["content"]["application/json"];
+/** `POST /api/v1/tunnel` 的请求体。 */
+export type OpenTunnelBody = NonNullable<operations["open-tunnel"]["requestBody"]>["content"]["application/json"];
+/** `POST /api/v1/tunnel/actions` 成功时的响应体。 */
+export type ActOnTunnelResult = operations["act-on-tunnel"]["responses"][200]["content"]["application/json"];
+/** `POST /api/v1/tunnel/actions` 的请求体。 */
+export type ActOnTunnelBody = NonNullable<operations["act-on-tunnel"]["requestBody"]>["content"]["application/json"];
+/** `PUT /api/v1/tunnel/plan` 成功时的响应体。 */
+export type ChangeTunnelPlanResult = operations["change-tunnel-plan"]["responses"][200]["content"]["application/json"];
+/** `PUT /api/v1/tunnel/plan` 的请求体。 */
+export type ChangeTunnelPlanBody = NonNullable<operations["change-tunnel-plan"]["requestBody"]>["content"]["application/json"];
+/** `GET /api/v1/tunnel/subscription` 成功时的响应体。 */
+export type GetTunnelSubscriptionResult = operations["get-tunnel-subscription"]["responses"][200]["content"]["application/json"];
+/** `POST /api/v1/tunnel/subscription/rotate` 成功时的响应体。 */
+export type RotateTunnelSubscriptionResult = operations["rotate-tunnel-subscription"]["responses"][200]["content"]["application/json"];
+/** `GET /api/v1/tunnel/usage` 成功时的响应体。 */
+export type GetTunnelUsageResult = operations["get-tunnel-usage"]["responses"][200]["content"]["application/json"];
+/** `GET /api/v1/tunnel/usage/series` 成功时的响应体。 */
+export type ListTunnelUsageSeriesResult = operations["list-tunnel-usage-series"]["responses"][200]["content"]["application/json"];

package/dist/tunnel/v1/index.js

@@ -0,0 +1,5 @@
+// 由 scripts/generate-ts.mjs 生成，不要手改。
+//
+// 别名把 operations[...] 那串下标换成一个名字。原始的 paths / components / operations 也
+// 一并导出：paths 是给 openapi-fetch 的 createClient<paths>() 用的。
+export {};