@leaflow/sdk 0.160.0 → 0.162.0

package/dist/compute/v1/generated/validators/zoneListResponseBody.zod.js

@@ -11,7 +11,7 @@
  * ## 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, a resource becomes `provisioning` and then reaches its usual status, such as `active` 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. Read the Checkout Session and the order in Billing for checkout and payment progress.
- * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the licensed and metered options Billing offers for them, in the currency of the project's current billing account, or null when the project has no billing account. They are list amounts before promotion codes, not a checkout guarantee. A purchase chooses one option with `billing`, which applies to all of its components. Every purchase and change has a quote operation beside it, at the same path followed by `/quote`, which returns what checkout would collect without ordering anything.
+ * - **Commercial terms.** Compute returns no amounts. Catalog items, such as instance types, disk types and public IP pools, and the region's own products carry `billing`: the Billing plan an order line for them is sold under, the dimensions the line carries, how its quantity is counted for each usage type, and the meters its metered price reads. Read their prices from Billing with `search-prices` and `search-rates`, quote a purchase or a change with Billing's `get-quote` using the same lines, and estimate metered usage with Billing's `estimate-usage`. A purchase chooses its terms with `billing`, which applies to all of its components.
  * - **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.
  * - **Operations.** Requests such as starting, stopping, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `operation` field names it; the field is null once the operation has finished, and the resource then shows 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 disk, 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.
  * - **Billing relationships.** A purchased resource records its `checkout_session_id` and, once checkout completes, its `order_id`, `order_item_id` and `subscription_id`. The subscription is `pending` until the order is accepted, `provisioning` while the resource is created, and `active` once it is delivered. Bandwidth is a property of its floating IP, not a separate resource. Snapshots use a purchased per-region count quota, and backups are metered on the region's backup service; neither has an order or subscription of its own.

package/dist/compute/v1/generated/validators/zoneResource.zod.d.ts

@@ -11,7 +11,7 @@
  * ## 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, a resource becomes `provisioning` and then reaches its usual status, such as `active` 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. Read the Checkout Session and the order in Billing for checkout and payment progress.
- * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the licensed and metered options Billing offers for them, in the currency of the project's current billing account, or null when the project has no billing account. They are list amounts before promotion codes, not a checkout guarantee. A purchase chooses one option with `billing`, which applies to all of its components. Every purchase and change has a quote operation beside it, at the same path followed by `/quote`, which returns what checkout would collect without ordering anything.
+ * - **Commercial terms.** Compute returns no amounts. Catalog items, such as instance types, disk types and public IP pools, and the region's own products carry `billing`: the Billing plan an order line for them is sold under, the dimensions the line carries, how its quantity is counted for each usage type, and the meters its metered price reads. Read their prices from Billing with `search-prices` and `search-rates`, quote a purchase or a change with Billing's `get-quote` using the same lines, and estimate metered usage with Billing's `estimate-usage`. A purchase chooses its terms with `billing`, which applies to all of its components.
  * - **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.
  * - **Operations.** Requests such as starting, stopping, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `operation` field names it; the field is null once the operation has finished, and the resource then shows 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 disk, 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.
  * - **Billing relationships.** A purchased resource records its `checkout_session_id` and, once checkout completes, its `order_id`, `order_item_id` and `subscription_id`. The subscription is `pending` until the order is accepted, `provisioning` while the resource is created, and `active` once it is delivered. Bandwidth is a property of its floating IP, not a separate resource. Snapshots use a purchased per-region count quota, and backups are metered on the region's backup service; neither has an order or subscription of its own.

package/dist/compute/v1/generated/validators/zoneResource.zod.js

@@ -11,7 +11,7 @@
  * ## 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, a resource becomes `provisioning` and then reaches its usual status, such as `active` 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. Read the Checkout Session and the order in Billing for checkout and payment progress.
- * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the licensed and metered options Billing offers for them, in the currency of the project's current billing account, or null when the project has no billing account. They are list amounts before promotion codes, not a checkout guarantee. A purchase chooses one option with `billing`, which applies to all of its components. Every purchase and change has a quote operation beside it, at the same path followed by `/quote`, which returns what checkout would collect without ordering anything.
+ * - **Commercial terms.** Compute returns no amounts. Catalog items, such as instance types, disk types and public IP pools, and the region's own products carry `billing`: the Billing plan an order line for them is sold under, the dimensions the line carries, how its quantity is counted for each usage type, and the meters its metered price reads. Read their prices from Billing with `search-prices` and `search-rates`, quote a purchase or a change with Billing's `get-quote` using the same lines, and estimate metered usage with Billing's `estimate-usage`. A purchase chooses its terms with `billing`, which applies to all of its components.
  * - **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.
  * - **Operations.** Requests such as starting, stopping, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `operation` field names it; the field is null once the operation has finished, and the resource then shows 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 disk, 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.
  * - **Billing relationships.** A purchased resource records its `checkout_session_id` and, once checkout completes, its `order_id`, `order_item_id` and `subscription_id`. The subscription is `pending` until the order is accepted, `provisioning` while the resource is created, and `active` once it is delivered. Bandwidth is a property of its floating IP, not a separate resource. Snapshots use a purchased per-region count quota, and backups are metered on the region's backup service; neither has an order or subscription of its own.

package/dist/membership/v1/generated/models.d.ts

@@ -52,13 +52,11 @@ export declare const PlanPriceInterval: {
     readonly year: "year";
 };
 /**
- * A price of the plan in Billing.
+ * A price of the plan in Billing. Membership returns no amounts; read the price from Billing with `get-price` or `search-prices` by `price_id`.
  */
 export interface PlanPrice {
     price_id: string;
     currency: Currency;
-    /** Charged for each period, before tax and discounts. */
-    unit_amount: Money;
     interval: PlanPriceInterval;
     /** @minimum 1 */
     interval_count: number;

package/dist/membership/v1/generated/validators/plan.zod.d.ts

@@ -15,7 +15,6 @@ export declare const Plan: zod.ZodObject<{
     prices: zod.ZodArray<zod.ZodObject<{
         price_id: zod.ZodUUID;
         currency: zod.ZodString;
-        unit_amount: zod.ZodString;
         interval: zod.ZodEnum<{
             month: "month";
             year: "year";

package/dist/membership/v1/generated/validators/planList.zod.d.ts

@@ -16,7 +16,6 @@ export declare const PlanList: zod.ZodObject<{
         prices: zod.ZodArray<zod.ZodObject<{
             price_id: zod.ZodUUID;
             currency: zod.ZodString;
-            unit_amount: zod.ZodString;
             interval: zod.ZodEnum<{
                 month: "month";
                 year: "year";

package/dist/membership/v1/generated/validators/planPrice.zod.d.ts

@@ -9,7 +9,6 @@ import * as zod from "zod";
 export declare const PlanPrice: zod.ZodObject<{
     price_id: zod.ZodUUID;
     currency: zod.ZodString;
-    unit_amount: zod.ZodString;
     interval: zod.ZodEnum<{
         month: "month";
         year: "year";

package/dist/membership/v1/generated/validators/planPrice.zod.js

@@ -7,13 +7,11 @@
  */
 import * as zod from "zod";
 import { Currency } from "./currency.zod.js";
-import { Money } from "./money.zod.js";
 export const PlanPrice = zod
     .strictObject({
     price_id: zod.uuid(),
     currency: Currency,
-    unit_amount: Money.describe("Charged for each period, before tax and discounts."),
     interval: zod.enum(["month", "year"]),
     interval_count: zod.int().min(1),
 })
-    .describe("A price of the plan in Billing.");
+    .describe("A price of the plan in Billing. Membership returns no amounts; read the price from Billing with `get-price` or `search-prices` by `price_id`.");

package/dist/routes.d.ts

@@ -1783,14 +1783,6 @@ export declare const routes: readonly [{
     readonly operationId: "restore-backup";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://compute.leaflow.cloud";
-}, {
-    readonly service: "compute";
-    readonly contract: "compute";
-    readonly method: "POST";
-    readonly path: "/api/v1/backups/{backupId}/restore/quote";
-    readonly operationId: "create-backup-restore-quote";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://compute.leaflow.cloud";
 }, {
     readonly service: "compute";
     readonly contract: "compute";
@@ -1823,14 +1815,6 @@ export declare const routes: readonly [{
     readonly operationId: "create-image";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://compute.leaflow.cloud";
-}, {
-    readonly service: "compute";
-    readonly contract: "compute";
-    readonly method: "POST";
-    readonly path: "/api/v1/images/quote";
-    readonly operationId: "create-image-quote";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://compute.leaflow.cloud";
 }, {
     readonly service: "compute";
     readonly contract: "compute";
@@ -1895,14 +1879,6 @@ export declare const routes: readonly [{
     readonly operationId: "create-disk";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://compute.leaflow.cloud";
-}, {
-    readonly service: "compute";
-    readonly contract: "compute";
-    readonly method: "POST";
-    readonly path: "/api/v1/disks/quote";
-    readonly operationId: "create-disk-quote";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://compute.leaflow.cloud";
 }, {
     readonly service: "compute";
     readonly contract: "compute";
@@ -1935,14 +1911,6 @@ export declare const routes: readonly [{
     readonly operationId: "resize-disk";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://compute.leaflow.cloud";
-}, {
-    readonly service: "compute";
-    readonly contract: "compute";
-    readonly method: "POST";
-    readonly path: "/api/v1/disks/{diskId}/resize/quote";
-    readonly operationId: "create-disk-resize-quote";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://compute.leaflow.cloud";
 }, {
     readonly service: "compute";
     readonly contract: "compute";
@@ -1967,14 +1935,6 @@ export declare const routes: readonly [{
     readonly operationId: "allocate-floating-ip";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://compute.leaflow.cloud";
-}, {
-    readonly service: "compute";
-    readonly contract: "compute";
-    readonly method: "POST";
-    readonly path: "/api/v1/floating-ips/quote";
-    readonly operationId: "create-floating-ip-quote";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://compute.leaflow.cloud";
 }, {
     readonly service: "compute";
     readonly contract: "compute";
@@ -1999,14 +1959,6 @@ export declare const routes: readonly [{
     readonly operationId: "set-floating-ip-bandwidth";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://compute.leaflow.cloud";
-}, {
-    readonly service: "compute";
-    readonly contract: "compute";
-    readonly method: "POST";
-    readonly path: "/api/v1/floating-ips/{floatingIpId}/bandwidth/quote";
-    readonly operationId: "create-floating-ip-bandwidth-quote";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://compute.leaflow.cloud";
 }, {
     readonly service: "compute";
     readonly contract: "compute";
@@ -2039,14 +1991,6 @@ export declare const routes: readonly [{
     readonly operationId: "launch-instance";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://compute.leaflow.cloud";
-}, {
-    readonly service: "compute";
-    readonly contract: "compute";
-    readonly method: "POST";
-    readonly path: "/api/v1/instances/quote";
-    readonly operationId: "create-instance-quote";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://compute.leaflow.cloud";
 }, {
     readonly service: "compute";
     readonly contract: "compute";
@@ -2143,14 +2087,6 @@ export declare const routes: readonly [{
     readonly operationId: "resize-instance";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://compute.leaflow.cloud";
-}, {
-    readonly service: "compute";
-    readonly contract: "compute";
-    readonly method: "POST";
-    readonly path: "/api/v1/instances/{instanceId}/resize/quote";
-    readonly operationId: "create-instance-resize-quote";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://compute.leaflow.cloud";
 }, {
     readonly service: "compute";
     readonly contract: "compute";
@@ -2466,9 +2402,9 @@ export declare const routes: readonly [{
 }, {
     readonly service: "compute";
     readonly contract: "compute";
-    readonly method: "POST";
-    readonly path: "/api/v1/regions/{regionId}/snapshot-quota/quote";
-    readonly operationId: "create-snapshot-quota-quote";
+    readonly method: "DELETE";
+    readonly path: "/api/v1/regions/{regionId}/snapshot-quota";
+    readonly operationId: "delete-snapshot-quota";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://compute.leaflow.cloud";
 }, {
@@ -2490,9 +2426,9 @@ export declare const routes: readonly [{
 }, {
     readonly service: "compute";
     readonly contract: "compute";
-    readonly method: "POST";
-    readonly path: "/api/v1/regions/{regionId}/backup-service/quote";
-    readonly operationId: "create-backup-service-quote";
+    readonly method: "DELETE";
+    readonly path: "/api/v1/regions/{regionId}/backup-service";
+    readonly operationId: "delete-backup-service";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://compute.leaflow.cloud";
 }, {
@@ -2514,9 +2450,9 @@ export declare const routes: readonly [{
 }, {
     readonly service: "compute";
     readonly contract: "compute";
-    readonly method: "POST";
-    readonly path: "/api/v1/regions/{regionId}/backup-capacity-packs/quote";
-    readonly operationId: "create-backup-capacity-pack-quote";
+    readonly method: "DELETE";
+    readonly path: "/api/v1/regions/{regionId}/backup-capacity-packs/{packId}";
+    readonly operationId: "delete-backup-capacity-pack";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://compute.leaflow.cloud";
 }, {

package/dist/routes.js

@@ -2008,15 +2008,6 @@ export const routes = [
         securityScheme: "ScopedToken",
         upstreamUrl: "https://compute.leaflow.cloud",
     },
-    {
-        service: "compute",
-        contract: "compute",
-        method: "POST",
-        path: "/api/v1/backups/{backupId}/restore/quote",
-        operationId: "create-backup-restore-quote",
-        securityScheme: "ScopedToken",
-        upstreamUrl: "https://compute.leaflow.cloud",
-    },
     {
         service: "compute",
         contract: "compute",
@@ -2053,15 +2044,6 @@ export const routes = [
         securityScheme: "ScopedToken",
         upstreamUrl: "https://compute.leaflow.cloud",
     },
-    {
-        service: "compute",
-        contract: "compute",
-        method: "POST",
-        path: "/api/v1/images/quote",
-        operationId: "create-image-quote",
-        securityScheme: "ScopedToken",
-        upstreamUrl: "https://compute.leaflow.cloud",
-    },
     {
         service: "compute",
         contract: "compute",
@@ -2134,15 +2116,6 @@ export const routes = [
         securityScheme: "ScopedToken",
         upstreamUrl: "https://compute.leaflow.cloud",
     },
-    {
-        service: "compute",
-        contract: "compute",
-        method: "POST",
-        path: "/api/v1/disks/quote",
-        operationId: "create-disk-quote",
-        securityScheme: "ScopedToken",
-        upstreamUrl: "https://compute.leaflow.cloud",
-    },
     {
         service: "compute",
         contract: "compute",
@@ -2179,15 +2152,6 @@ export const routes = [
         securityScheme: "ScopedToken",
         upstreamUrl: "https://compute.leaflow.cloud",
     },
-    {
-        service: "compute",
-        contract: "compute",
-        method: "POST",
-        path: "/api/v1/disks/{diskId}/resize/quote",
-        operationId: "create-disk-resize-quote",
-        securityScheme: "ScopedToken",
-        upstreamUrl: "https://compute.leaflow.cloud",
-    },
     {
         service: "compute",
         contract: "compute",
@@ -2215,15 +2179,6 @@ export const routes = [
         securityScheme: "ScopedToken",
         upstreamUrl: "https://compute.leaflow.cloud",
     },
-    {
-        service: "compute",
-        contract: "compute",
-        method: "POST",
-        path: "/api/v1/floating-ips/quote",
-        operationId: "create-floating-ip-quote",
-        securityScheme: "ScopedToken",
-        upstreamUrl: "https://compute.leaflow.cloud",
-    },
     {
         service: "compute",
         contract: "compute",
@@ -2251,15 +2206,6 @@ export const routes = [
         securityScheme: "ScopedToken",
         upstreamUrl: "https://compute.leaflow.cloud",
     },
-    {
-        service: "compute",
-        contract: "compute",
-        method: "POST",
-        path: "/api/v1/floating-ips/{floatingIpId}/bandwidth/quote",
-        operationId: "create-floating-ip-bandwidth-quote",
-        securityScheme: "ScopedToken",
-        upstreamUrl: "https://compute.leaflow.cloud",
-    },
     {
         service: "compute",
         contract: "compute",
@@ -2296,15 +2242,6 @@ export const routes = [
         securityScheme: "ScopedToken",
         upstreamUrl: "https://compute.leaflow.cloud",
     },
-    {
-        service: "compute",
-        contract: "compute",
-        method: "POST",
-        path: "/api/v1/instances/quote",
-        operationId: "create-instance-quote",
-        securityScheme: "ScopedToken",
-        upstreamUrl: "https://compute.leaflow.cloud",
-    },
     {
         service: "compute",
         contract: "compute",
@@ -2413,15 +2350,6 @@ export const routes = [
         securityScheme: "ScopedToken",
         upstreamUrl: "https://compute.leaflow.cloud",
     },
-    {
-        service: "compute",
-        contract: "compute",
-        method: "POST",
-        path: "/api/v1/instances/{instanceId}/resize/quote",
-        operationId: "create-instance-resize-quote",
-        securityScheme: "ScopedToken",
-        upstreamUrl: "https://compute.leaflow.cloud",
-    },
     {
         service: "compute",
         contract: "compute",
@@ -2776,9 +2704,9 @@ export const routes = [
     {
         service: "compute",
         contract: "compute",
-        method: "POST",
-        path: "/api/v1/regions/{regionId}/snapshot-quota/quote",
-        operationId: "create-snapshot-quota-quote",
+        method: "DELETE",
+        path: "/api/v1/regions/{regionId}/snapshot-quota",
+        operationId: "delete-snapshot-quota",
         securityScheme: "ScopedToken",
         upstreamUrl: "https://compute.leaflow.cloud",
     },
@@ -2803,9 +2731,9 @@ export const routes = [
     {
         service: "compute",
         contract: "compute",
-        method: "POST",
-        path: "/api/v1/regions/{regionId}/backup-service/quote",
-        operationId: "create-backup-service-quote",
+        method: "DELETE",
+        path: "/api/v1/regions/{regionId}/backup-service",
+        operationId: "delete-backup-service",
         securityScheme: "ScopedToken",
         upstreamUrl: "https://compute.leaflow.cloud",
     },
@@ -2830,9 +2758,9 @@ export const routes = [
     {
         service: "compute",
         contract: "compute",
-        method: "POST",
-        path: "/api/v1/regions/{regionId}/backup-capacity-packs/quote",
-        operationId: "create-backup-capacity-pack-quote",
+        method: "DELETE",
+        path: "/api/v1/regions/{regionId}/backup-capacity-packs/{packId}",
+        operationId: "delete-backup-capacity-pack",
         securityScheme: "ScopedToken",
         upstreamUrl: "https://compute.leaflow.cloud",
     },

package/package.json

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

package/dist/compute/v1/generated/validators/allocateFloatingIPQuoteRequestBody.zod.js

@@ -1,44 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Compute API
- * Leaflow Compute user API for managing instances, disks, snapshots, backups, images, private networks, subnets, routes, security groups, network interfaces and floating IPs.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `scopedTokenAuth` security scheme.
- *
- * ## 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, a resource becomes `provisioning` and then reaches its usual status, such as `active` 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. Read the Checkout Session and the order in Billing for checkout and payment progress.
- * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the licensed and metered options Billing offers for them, in the currency of the project's current billing account, or null when the project has no billing account. They are list amounts before promotion codes, not a checkout guarantee. A purchase chooses one option with `billing`, which applies to all of its components. Every purchase and change has a quote operation beside it, at the same path followed by `/quote`, which returns what checkout would collect without ordering anything.
- * - **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.
- * - **Operations.** Requests such as starting, stopping, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `operation` field names it; the field is null once the operation has finished, and the resource then shows 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 disk, 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.
- * - **Billing relationships.** A purchased resource records its `checkout_session_id` and, once checkout completes, its `order_id`, `order_item_id` and `subscription_id`. The subscription is `pending` until the order is accepted, `provisioning` while the resource is created, and `active` once it is delivered. Bandwidth is a property of its floating IP, not a separate resource. Snapshots use a purchased per-region count quota, and backups are metered on the region's backup service; neither has an order or subscription of its own.
- * - **Availability zones.** A disk and an instance must reside in the same availability zone to be attached. Instance types and disk types are each bound to one availability zone, so choosing a type determines the zone.
- * - **IPv6 is not sold separately.** Once enabled on a private network, IPv6 addresses are assigned to the instances in that network automatically; they can be neither requested nor released individually.
- * - **Floating IPs have a cooldown period.** A released address is neither available for re-allocation nor handed to another user for some time, so that DNS records and allow-lists still pointing at it do not break immediately.
- * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-import { BillingChoice } from "./billingChoice.zod.js";
-export const allocateFloatingIPQuoteRequestBodyAddressMax = 64;
-export const allocateFloatingIPQuoteRequestBodyBandwidthMbpsMax = 1000;
-export const AllocateFloatingIPQuoteRequestBody = zod
-    .strictObject({
-    address: zod
-        .string()
-        .max(allocateFloatingIPQuoteRequestBodyAddressMax)
-        .optional()
-        .describe("The address to allocate. Allocated by the platform when omitted"),
-    bandwidth_mbps: zod
-        .int()
-        .min(1)
-        .max(allocateFloatingIPQuoteRequestBodyBandwidthMbpsMax)
-        .describe("The bandwidth ceiling of this address, in Mbit/s, applied to both directions.\n\nRequired, and there is no \"unlimited\": an address with no ceiling runs at line rate and is\ncharged nothing for the traffic, while the address itself bills normally — so the invoice\nlooks correct and nothing anywhere reports it.\n\nIt is part of this floating IP purchase and is billed as the pool's `bandwidth_pricing` shows,\nwith the purchase's billing choice. Changing it later updates the\nsame floating IP through its bandwidth endpoint, not an independent bandwidth resource."),
-    private_network_id: zod.uuid(),
-    ipv4_pool_id: zod.uuid(),
-    billing: BillingChoice,
-})
-    .describe("The request of `allocate-floating-ip`, without `checkout`.");

package/dist/compute/v1/generated/validators/createBackupCapacityPackQuoteRequestBody.zod.d.ts

@@ -1,46 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Compute API
- * Leaflow Compute user API for managing instances, disks, snapshots, backups, images, private networks, subnets, routes, security groups, network interfaces and floating IPs.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `scopedTokenAuth` security scheme.
- *
- * ## 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, a resource becomes `provisioning` and then reaches its usual status, such as `active` 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. Read the Checkout Session and the order in Billing for checkout and payment progress.
- * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the licensed and metered options Billing offers for them, in the currency of the project's current billing account, or null when the project has no billing account. They are list amounts before promotion codes, not a checkout guarantee. A purchase chooses one option with `billing`, which applies to all of its components. Every purchase and change has a quote operation beside it, at the same path followed by `/quote`, which returns what checkout would collect without ordering anything.
- * - **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.
- * - **Operations.** Requests such as starting, stopping, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `operation` field names it; the field is null once the operation has finished, and the resource then shows 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 disk, 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.
- * - **Billing relationships.** A purchased resource records its `checkout_session_id` and, once checkout completes, its `order_id`, `order_item_id` and `subscription_id`. The subscription is `pending` until the order is accepted, `provisioning` while the resource is created, and `active` once it is delivered. Bandwidth is a property of its floating IP, not a separate resource. Snapshots use a purchased per-region count quota, and backups are metered on the region's backup service; neither has an order or subscription of its own.
- * - **Availability zones.** A disk and an instance must reside in the same availability zone to be attached. Instance types and disk types are each bound to one availability zone, so choosing a type determines the zone.
- * - **IPv6 is not sold separately.** Once enabled on a private network, IPv6 addresses are assigned to the instances in that network automatically; they can be neither requested nor released individually.
- * - **Floating IPs have a cooldown period.** A released address is neither available for re-allocation nor handed to another user for some time, so that DNS records and allow-lists still pointing at it do not break immediately.
- * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export declare const CreateBackupCapacityPackQuoteRequestBody: zod.ZodObject<{
-    capacity_gib: zod.ZodInt;
-    billing: zod.ZodObject<{
-        usage_type: zod.ZodEnum<{
-            licensed: "licensed";
-            metered: "metered";
-        }>;
-        period: zod.ZodOptional<zod.ZodObject<{
-            unit: zod.ZodEnum<{
-                month: "month";
-                year: "year";
-            }>;
-            count: zod.ZodInt;
-        }, zod.z.core.$strict>>;
-        termination_policy: zod.ZodOptional<zod.ZodEnum<{
-            immediate: "immediate";
-            period_end: "period_end";
-        }>>;
-    }, zod.z.core.$strict>;
-}, zod.z.core.$strict>;
-export type CreateBackupCapacityPackQuoteRequestBody = zod.input<typeof CreateBackupCapacityPackQuoteRequestBody>;
-export type CreateBackupCapacityPackQuoteRequestBodyOutput = zod.output<typeof CreateBackupCapacityPackQuoteRequestBody>;

package/dist/compute/v1/generated/validators/createDiskQuoteRequestBody.zod.d.ts

@@ -1,51 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Compute API
- * Leaflow Compute user API for managing instances, disks, snapshots, backups, images, private networks, subnets, routes, security groups, network interfaces and floating IPs.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `scopedTokenAuth` security scheme.
- *
- * ## 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, a resource becomes `provisioning` and then reaches its usual status, such as `active` 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. Read the Checkout Session and the order in Billing for checkout and payment progress.
- * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the licensed and metered options Billing offers for them, in the currency of the project's current billing account, or null when the project has no billing account. They are list amounts before promotion codes, not a checkout guarantee. A purchase chooses one option with `billing`, which applies to all of its components. Every purchase and change has a quote operation beside it, at the same path followed by `/quote`, which returns what checkout would collect without ordering anything.
- * - **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.
- * - **Operations.** Requests such as starting, stopping, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `operation` field names it; the field is null once the operation has finished, and the resource then shows 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 disk, 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.
- * - **Billing relationships.** A purchased resource records its `checkout_session_id` and, once checkout completes, its `order_id`, `order_item_id` and `subscription_id`. The subscription is `pending` until the order is accepted, `provisioning` while the resource is created, and `active` once it is delivered. Bandwidth is a property of its floating IP, not a separate resource. Snapshots use a purchased per-region count quota, and backups are metered on the region's backup service; neither has an order or subscription of its own.
- * - **Availability zones.** A disk and an instance must reside in the same availability zone to be attached. Instance types and disk types are each bound to one availability zone, so choosing a type determines the zone.
- * - **IPv6 is not sold separately.** Once enabled on a private network, IPv6 addresses are assigned to the instances in that network automatically; they can be neither requested nor released individually.
- * - **Floating IPs have a cooldown period.** A released address is neither available for re-allocation nor handed to another user for some time, so that DNS records and allow-lists still pointing at it do not break immediately.
- * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export declare const createDiskQuoteRequestBodyDiskTypeIdMax = 64;
-export declare const createDiskQuoteRequestBodyNameMax = 128;
-export declare const CreateDiskQuoteRequestBody: zod.ZodObject<{
-    disk_type_id: zod.ZodUUID;
-    name: zod.ZodString;
-    size_gb: zod.ZodInt;
-    snapshot_id: zod.ZodOptional<zod.ZodUUID>;
-    billing: zod.ZodObject<{
-        usage_type: zod.ZodEnum<{
-            licensed: "licensed";
-            metered: "metered";
-        }>;
-        period: zod.ZodOptional<zod.ZodObject<{
-            unit: zod.ZodEnum<{
-                month: "month";
-                year: "year";
-            }>;
-            count: zod.ZodInt;
-        }, zod.z.core.$strict>>;
-        termination_policy: zod.ZodOptional<zod.ZodEnum<{
-            immediate: "immediate";
-            period_end: "period_end";
-        }>>;
-    }, zod.z.core.$strict>;
-}, zod.z.core.$strict>;
-export type CreateDiskQuoteRequestBody = zod.input<typeof CreateDiskQuoteRequestBody>;
-export type CreateDiskQuoteRequestBodyOutput = zod.output<typeof CreateDiskQuoteRequestBody>;