@leaflow/sdk 0.0.0-dev.381.g84c72f5 → 0.0.0-dev.385.g78d513c

package/dist/tunnel/v1/generated/validators/usageSeriesResource.zod.d.ts

@@ -1,48 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Tunnel API
- * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
- *
- * ## Layer 4 only
- *
- * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
- *
- * ## Layer 4 is entitled per project, and no project holds it by default
- *
- * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
- *
- * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme.
- *
- * ## Conventions
- *
- * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
- *
- * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
- *
- * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
- *
- * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
- *
- * - **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.
- *
- * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
- *
- * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export declare const UsageSeriesResource: zod.ZodObject<{
-    days: zod.ZodInt;
-    points: zod.ZodArray<zod.ZodObject<{
-        billed_bytes: zod.ZodInt;
-        day: zod.ZodString;
-        raw_bytes: zod.ZodInt;
-    }, zod.z.core.$strict>>;
-}, zod.z.core.$strict>;
-export type UsageSeriesResource = zod.input<typeof UsageSeriesResource>;
-export type UsageSeriesResourceOutput = zod.output<typeof UsageSeriesResource>;

package/dist/tunnel/v1/generated/validators/usageSeriesResource.zod.js

@@ -1,45 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Tunnel API
- * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
- *
- * ## Layer 4 only
- *
- * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
- *
- * ## Layer 4 is entitled per project, and no project holds it by default
- *
- * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
- *
- * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme.
- *
- * ## Conventions
- *
- * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
- *
- * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
- *
- * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
- *
- * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
- *
- * - **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.
- *
- * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
- *
- * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-import { UsageDayResource } from "./usageDayResource.zod.js";
-export const UsageSeriesResource = zod.strictObject({
-    days: zod
-        .int()
-        .describe("The number of days actually covered, which may have been clamped to the range 1–365"),
-    points: zod.array(UsageDayResource),
-});

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

@@ -1,3 +0,0 @@
-export * from "./generated/functions.js";
-export * from "./generated/models.js";
-export * as schemas from "./generated/schemas.zod.js";

package/dist/tunnel/v1/index.js

@@ -1,3 +0,0 @@
-export * from "./generated/functions.js";
-export * from "./generated/models.js";
-export * as schemas from "./generated/schemas.zod.js";