@leaflow/sdk 0.160.0 → 0.162.0

package/dist/compute/v1/generated/validators/createImageQuoteRequestBody.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 CreateImageQuoteRequestBody: zod.ZodObject<{
-    instance_id: 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 CreateImageQuoteRequestBody = zod.input<typeof CreateImageQuoteRequestBody>;
-export type CreateImageQuoteRequestBodyOutput = zod.output<typeof CreateImageQuoteRequestBody>;

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

@@ -1,35 +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 { Money } from "./money.zod.js";
-export const Funds = zod
-    .strictObject({
-    available_balance_amount: Money.describe("Spendable balance after pending returns."),
-    usable_credit_amount: Money.describe("Currently effective credits eligible for the quoted purchases or metered usage. Each grant is counted once."),
-    restricted_credit_amount: Money.describe("Currently effective credits that cannot fund any quoted purchase or metered target. Unused eligible credits are not restricted."),
-    required_balance_amount: Money.describe("Minimum spendable balance needed after eligible credits, covering immediate charges and every new metered purchase's admission requirement."),
-    balance_shortfall_amount: Money.describe("Additional balance needed now. Zero means account funds satisfy this quote. No funds are reserved."),
-    required_top_up_amount: Money.describe("Minimum recharge that covers the shortfall, respecting the currency minimum recharge and currency precision. Zero when no additional balance is needed."),
-})
-    .describe("Account funding for this purchase, calculated by Billing. Amounts use the enclosing response currency.\nCredit eligibility and all purchase requirements are already evaluated. Nothing is charged or reserved.\nA licensed purchase may instead be paid with an online payment method.\n");

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

@@ -1,113 +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 launchInstanceQuoteRequestBodyCountDefault = 1;
-export declare const launchInstanceQuoteRequestBodyCountMax = 20;
-export declare const launchInstanceQuoteRequestBodyNameMax = 128;
-export declare const launchInstanceQuoteRequestBodyPasswordMax = 128;
-export declare const LaunchInstanceQuoteRequestBody: zod.ZodObject<{
-    floating_ip_id: zod.ZodOptional<zod.ZodUUID>;
-    count: zod.ZodDefault<zod.ZodInt>;
-    generate_password: zod.ZodOptional<zod.ZodBoolean>;
-    compute: zod.ZodObject<{
-        instance_type_id: 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>;
-    name: zod.ZodString;
-    password: zod.ZodOptional<zod.ZodString>;
-    port_id: zod.ZodOptional<zod.ZodUUID>;
-    security_group_ids: zod.ZodOptional<zod.ZodNullable<zod.ZodArray<zod.ZodUUID>>>;
-    subnet_id: zod.ZodOptional<zod.ZodUUID>;
-    boot_disk: zod.ZodDiscriminatedUnion<[zod.ZodObject<{
-        type: zod.ZodEnum<{
-            image: "image";
-        }>;
-        image_id: zod.ZodUUID;
-        disk_type_id: zod.ZodUUID;
-        size_gb: zod.ZodInt;
-        delete_with_instance: zod.ZodDefault<zod.ZodBoolean>;
-        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>, zod.ZodObject<{
-        type: zod.ZodEnum<{
-            disk: "disk";
-        }>;
-        disk_id: zod.ZodUUID;
-        login_username: zod.ZodString;
-    }, zod.z.core.$strict>], "type">;
-    floating_ip: zod.ZodOptional<zod.ZodObject<{
-        bandwidth_mbps: zod.ZodInt;
-        ipv4_pool_id: 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>>;
-}, zod.z.core.$strict>;
-export type LaunchInstanceQuoteRequestBody = zod.input<typeof LaunchInstanceQuoteRequestBody>;
-export type LaunchInstanceQuoteRequestBodyOutput = zod.output<typeof LaunchInstanceQuoteRequestBody>;

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

@@ -1,71 +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 { BootDisk } from "./bootDisk.zod.js";
-import { NewCompute } from "./newCompute.zod.js";
-import { NewFloatingIP } from "./newFloatingIP.zod.js";
-export const launchInstanceQuoteRequestBodyCountDefault = 1;
-export const launchInstanceQuoteRequestBodyCountMax = 20;
-export const launchInstanceQuoteRequestBodyNameMax = 128;
-export const launchInstanceQuoteRequestBodyPasswordMax = 128;
-export const LaunchInstanceQuoteRequestBody = zod
-    .strictObject({
-    floating_ip_id: zod
-        .uuid()
-        .optional()
-        .describe("Bind a floating IP you already hold, instead of allocating a new one. It must be idle and in\nthe same region.\n\nMutually exclusive with `bandwidth_mbps`: an address you already hold has its own bandwidth\nceiling, set when it was allocated, and changing it is a separate operation.\n\nLike `bandwidth_mbps`, this happens **inside the creation**: if binding fails, no instance is\ncreated. Binding afterwards is still possible from the instance page, but then it is two\noperations and a failure in between leaves an instance you cannot reach.\n\nOnly one instance can be created when it is used — one address binds to one interface."),
-    count: zod
-        .int()
-        .min(1)
-        .max(launchInstanceQuoteRequestBodyCountMax)
-        .default(launchInstanceQuoteRequestBodyCountDefault)
-        .describe("Number of instances to create; 1 when omitted. Names are numbered automatically for several"),
-    generate_password: zod
-        .boolean()
-        .optional()
-        .describe("Have the platform generate a random password, returned only in this response"),
-    compute: NewCompute,
-    name: zod.string().min(1).max(launchInstanceQuoteRequestBodyNameMax),
-    password: zod
-        .string()
-        .max(launchInstanceQuoteRequestBodyPasswordMax)
-        .optional()
-        .describe("The password to set, on the login account and on root. Only the SSH public keys of the project are used when omitted"),
-    port_id: zod
-        .uuid()
-        .optional()
-        .describe("Use an existing network interface, which may already have a floating IP bound. Exactly one of this and `subnet_id`; only one instance can be created when it is used"),
-    security_group_ids: zod
-        .array(zod.uuid())
-        .min(1)
-        .nullish()
-        .describe("Required when a primary network interface is created, at least one; the default security group is not applied automatically. Ignored together with `port_id`, as the security groups of that interface were fixed when it was created"),
-    subnet_id: zod
-        .uuid()
-        .optional()
-        .describe("Create the primary network interface in this subnet. Exactly one of this and `port_id`"),
-    boot_disk: BootDisk,
-    floating_ip: NewFloatingIP.optional(),
-})
-    .describe("The request of `launch-instance`, without `checkout`.");

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

@@ -1,54 +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 Pricing: zod.ZodObject<{
-    currency: zod.ZodString;
-    options: zod.ZodArray<zod.ZodObject<{
-        usage_type: zod.ZodEnum<{
-            licensed: "licensed";
-            metered: "metered";
-        }>;
-        period: zod.ZodUnion<readonly [zod.ZodObject<{
-            unit: zod.ZodEnum<{
-                month: "month";
-                year: "year";
-            }>;
-            count: zod.ZodInt;
-        }, zod.z.core.$strict>, zod.ZodNull]>;
-        quantity_unit: zod.ZodEnum<{
-            item: "item";
-            gib: "gib";
-            mbps: "mbps";
-            snapshot: "snapshot";
-        }>;
-        amount: zod.ZodNullable<zod.ZodString>;
-        monthly_amount: zod.ZodNullable<zod.ZodString>;
-        saving_percent: zod.ZodNullable<zod.ZodString>;
-        unit_amount: zod.ZodNullable<zod.ZodString>;
-        unit: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"hour">, zod.ZodLiteral<null>]>>;
-        termination_policy: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"immediate">, zod.ZodLiteral<"period_end">, zod.ZodLiteral<null>]>>;
-    }, zod.z.core.$strict>>;
-}, zod.z.core.$strict>;
-export type Pricing = zod.input<typeof Pricing>;
-export type PricingOutput = zod.output<typeof Pricing>;

package/dist/compute/v1/generated/validators/pricingOption.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 PricingOption: zod.ZodObject<{
-    usage_type: zod.ZodEnum<{
-        licensed: "licensed";
-        metered: "metered";
-    }>;
-    period: zod.ZodUnion<readonly [zod.ZodObject<{
-        unit: zod.ZodEnum<{
-            month: "month";
-            year: "year";
-        }>;
-        count: zod.ZodInt;
-    }, zod.z.core.$strict>, zod.ZodNull]>;
-    quantity_unit: zod.ZodEnum<{
-        item: "item";
-        gib: "gib";
-        mbps: "mbps";
-        snapshot: "snapshot";
-    }>;
-    amount: zod.ZodNullable<zod.ZodString>;
-    monthly_amount: zod.ZodNullable<zod.ZodString>;
-    saving_percent: zod.ZodNullable<zod.ZodString>;
-    unit_amount: zod.ZodNullable<zod.ZodString>;
-    unit: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"hour">, zod.ZodLiteral<null>]>>;
-    termination_policy: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"immediate">, zod.ZodLiteral<"period_end">, zod.ZodLiteral<null>]>>;
-}, zod.z.core.$strict>;
-export type PricingOption = zod.input<typeof PricingOption>;
-export type PricingOptionOutput = zod.output<typeof PricingOption>;

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

@@ -1,62 +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 { BillingPeriod } from "./billingPeriod.zod.js";
-export const PricingOption = zod
-    .strictObject({
-    usage_type: zod
-        .enum(["licensed", "metered"])
-        .describe("`licensed` pays for a period in advance; `metered` bills usage until canceled."),
-    period: zod
-        .union([BillingPeriod, zod.null()])
-        .describe("The term of a licensed option; null for metered."),
-    quantity_unit: zod
-        .enum(["item", "gib", "mbps", "snapshot"])
-        .describe("What the amounts are for: one `item`, such as an instance or an address; one `gib` of size or capacity; one `mbps` of bandwidth; or one `snapshot` slot."),
-    amount: zod
-        .string()
-        .nullable()
-        .describe("Licensed only; null for metered. The amount for one period, per quantity unit."),
-    monthly_amount: zod
-        .string()
-        .nullable()
-        .describe("Licensed only; null for metered. `amount` spread over the months of the period."),
-    saving_percent: zod
-        .string()
-        .nullable()
-        .describe("Licensed only. How much lower `monthly_amount` is than that of the shortest licensed period of the same item, as a decimal percentage. Null for that shortest period and for metered."),
-    unit_amount: zod
-        .string()
-        .nullable()
-        .describe("Metered only; null for licensed. The amount for one `unit` of time, per quantity unit."),
-    unit: zod
-        .union([zod.literal("hour"), zod.literal(null)])
-        .nullable()
-        .describe("Metered only; null for licensed. The time unit of `unit_amount`."),
-    termination_policy: zod
-        .union([zod.literal("immediate"), zod.literal("period_end"), zod.literal(null)])
-        .nullable()
-        .describe("What canceling does under this option: `immediate` ends the service at once, with any refund following the option's terms; `period_end` ends it at the end of the paid period. Null means no explicit policy was recorded; it must not be interpreted as immediate."),
-})
-    .describe("One way to buy an item. Choose it by giving its usage_type, period and termination_policy as billing.");

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

@@ -1,81 +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 Quote: zod.ZodObject<{
-    funds: zod.ZodUnion<readonly [zod.ZodObject<{
-        available_balance_amount: zod.ZodString;
-        usable_credit_amount: zod.ZodString;
-        restricted_credit_amount: zod.ZodString;
-        required_balance_amount: zod.ZodString;
-        balance_shortfall_amount: zod.ZodString;
-        required_top_up_amount: zod.ZodString;
-    }, zod.z.core.$strict>, zod.ZodNull]>;
-    tax_status: zod.ZodEnum<{
-        complete: "complete";
-        requires_location_inputs: "requires_location_inputs";
-    }>;
-    items: zod.ZodArray<zod.ZodObject<{
-        product_id: zod.ZodString;
-        plan_id: zod.ZodUUID;
-        plan_name: zod.ZodString;
-        price_id: zod.ZodUUID;
-        dimensions: zod.ZodRecord<zod.ZodString, zod.ZodString>;
-        type: zod.ZodEnum<{
-            one_time: "one_time";
-            recurring: "recurring";
-        }>;
-        usage_type: zod.ZodEnum<{
-            licensed: "licensed";
-            metered: "metered";
-        }>;
-        interval: zod.ZodEnum<{
-            none: "none";
-            day: "day";
-            month: "month";
-            year: "year";
-        }>;
-        interval_count: zod.ZodNullable<zod.ZodInt>;
-        setup_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
-        recurring_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
-        unit_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
-        quantity: zod.ZodString;
-        amount: zod.ZodString;
-        discount_amount: zod.ZodString;
-        tax_amount: zod.ZodString;
-        tax_included_amount: zod.ZodString;
-        total: zod.ZodString;
-        estimated_usage_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
-        currency: zod.ZodString;
-    }, zod.z.core.$strict>>;
-    subtotal: zod.ZodString;
-    discount_amount: zod.ZodString;
-    tax_amount: zod.ZodString;
-    total: zod.ZodString;
-    estimated_usage_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
-    currency: zod.ZodString;
-    proration_date: zod.ZodNullable<zod.z.ZodISODateTime>;
-    refundable_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
-}, zod.z.core.$strict>;
-export type Quote = zod.input<typeof Quote>;
-export type QuoteOutput = zod.output<typeof Quote>;

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

@@ -1,53 +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 { Funds } from "./funds.zod.js";
-import { Money } from "./money.zod.js";
-import { QuoteItem } from "./quoteItem.zod.js";
-export const Quote = zod
-    .strictObject({
-    funds: zod.union([Funds, zod.null()]).describe("Null for a quote without a billing account."),
-    tax_status: zod
-        .enum(["complete", "requires_location_inputs"])
-        .describe("`complete`: tax is calculated for the billing account's invoice contact. `requires_location_inputs`: a quote without a billing account, which leaves out tax that would be added; tax already contained in a price is included."),
-    items: zod
-        .array(QuoteItem)
-        .describe("One line for each item the purchase would order, in the order it would order them."),
-    subtotal: Money.describe("Sum of line amounts before discounts, less tax already included in the discounted line\namounts, as on an invoice."),
-    discount_amount: Money.describe("Sum of line discounts."),
-    tax_amount: Money.describe("Sum of tax on the discounted line amounts."),
-    total: Money.describe("subtotal minus discount_amount plus tax_amount: what checkout collects, before applying\ncredit grants or balance. Equals the sum of line totals and excludes estimated_usage_amount."),
-    estimated_usage_amount: zod
-        .union([Money, zod.null()])
-        .describe("Sum of the lines' estimated_usage_amount. A projection, not part of total and not collected at\ncheckout. Null when no usage estimate is requested."),
-    currency: zod.string(),
-    proration_date: zod.iso
-        .datetime({ offset: true })
-        .nullable()
-        .describe("Changes only; null otherwise. The instant the change is priced from. Pass it with the change so the\norder is priced from the same instant."),
-    refundable_amount: zod
-        .union([Money, zod.null()])
-        .describe("Changes that lower the price only; null otherwise. What the change would return to the original\npayment sources, including the tax paid on it. total is zero for such a change."),
-})
-    .describe("A price preview for the purchase described by a service, calculated by Billing. Nothing is saved,\ncharged or reserved, and no discount redemption is consumed. Account discounts and tax are\nevaluated as for automatic checkout. Promotion codes are evaluated by Billing at checkout, not here.\nAll amounts use currency. This preview does not lock prices or guarantee discount availability.\nSuccess includes complete checkout amounts and every requested usage estimate. If any item or\nrequested usage estimate cannot be calculated, the operation returns its existing structured\nerror response; it never returns a partial quote with HTTP 200. A quote without a billing account\nhas no funds and no account discount, and leaves out tax that would be added.");