@leaflow/sdk 0.0.0-dev.410.gb8719fe → 0.0.0-dev.415.gb9e4b83

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

@@ -1,121 +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.
- * - **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 and rates from Billing with `search-prices`, 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.
- * - **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 launchInstanceRequestBodyCountDefault = 1;
-export declare const launchInstanceRequestBodyCountMax = 20;
-export declare const launchInstanceRequestBodyNameMax = 128;
-export declare const launchInstanceRequestBodyPasswordMax = 128;
-export declare const LaunchInstanceRequestBody: 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>;
-    checkout: zod.ZodOptional<zod.ZodObject<{
-        mode: zod.ZodDefault<zod.ZodEnum<{
-            automatic: "automatic";
-            deferred: "deferred";
-        }>>;
-        expected_amount: zod.ZodOptional<zod.ZodIntersection<zod.ZodString, zod.ZodString>>;
-        return_url: zod.ZodOptional<zod.ZodURL>;
-    }, zod.z.core.$strict>>;
-    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 LaunchInstanceRequestBody = zod.input<typeof LaunchInstanceRequestBody>;
-export type LaunchInstanceRequestBodyOutput = zod.output<typeof LaunchInstanceRequestBody>;

package/dist/compute/v1/generated/validators/launchInstanceRequestBody.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.
- * - **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 and rates from Billing with `search-prices`, 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.
- * - **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 { CheckoutOptions } from "./checkoutOptions.zod.js";
-import { NewCompute } from "./newCompute.zod.js";
-import { NewFloatingIP } from "./newFloatingIP.zod.js";
-export const launchInstanceRequestBodyCountDefault = 1;
-export const launchInstanceRequestBodyCountMax = 20;
-export const launchInstanceRequestBodyNameMax = 128;
-export const launchInstanceRequestBodyPasswordMax = 128;
-export const LaunchInstanceRequestBody = 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(launchInstanceRequestBodyCountMax)
-        .default(launchInstanceRequestBodyCountDefault)
-        .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(launchInstanceRequestBodyNameMax),
-    password: zod
-        .string()
-        .max(launchInstanceRequestBodyPasswordMax)
-        .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`"),
-    checkout: CheckoutOptions.optional(),
-    boot_disk: BootDisk,
-    floating_ip: NewFloatingIP.optional(),
-});

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

@@ -1,125 +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.
- * - **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 and rates from Billing with `search-prices`, 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.
- * - **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 launchInstanceResponseBodyInstancesMax = 20;
-export declare const LaunchInstanceResponseBody: zod.ZodObject<{
-    instances: zod.ZodArray<zod.ZodObject<{
-        availability_zone_id: zod.ZodUUID;
-        created_at: zod.z.ZodISODateTime;
-        hostname: zod.ZodString;
-        id: zod.ZodUUID;
-        image_id: zod.ZodNullable<zod.ZodUUID>;
-        instance_type_id: zod.ZodUUID;
-        ipv6_address: zod.ZodNullable<zod.ZodString>;
-        labels: zod.ZodRecord<zod.ZodString, zod.ZodString>;
-        login_username: zod.ZodString;
-        name: zod.ZodString;
-        notes: zod.ZodString;
-        private_ip: zod.ZodNullable<zod.ZodString>;
-        private_network_id: zod.ZodNullable<zod.ZodUUID>;
-        public_ips: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-        region_id: zod.ZodUUID;
-        status: zod.ZodEnum<{
-            active: "active";
-            deleted: "deleted";
-            error: "error";
-            unknown: "unknown";
-            failed: "failed";
-            pending: "pending";
-            paused: "paused";
-            stopped: "stopped";
-            suspended: "suspended";
-            provisioning: "provisioning";
-            shelved: "shelved";
-            shelved_offloaded: "shelved_offloaded";
-            rescued: "rescued";
-            missing: "missing";
-        }>;
-        subnet_id: zod.ZodNullable<zod.ZodUUID>;
-        updated_at: zod.z.ZodISODateTime;
-        generation: zod.ZodInt;
-        observed_at: zod.ZodNullable<zod.z.ZodISODateTime>;
-        restrictions: zod.ZodArray<zod.ZodObject<{
-            id: zod.ZodUUID;
-            source: zod.ZodEnum<{
-                operator: "operator";
-                billing: "billing";
-                iam: "iam";
-            }>;
-            source_id: zod.ZodString;
-            reason_code: zod.ZodString;
-            created_at: zod.z.ZodISODateTime;
-        }, zod.z.core.$strict>>;
-        failure_reason: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"checkout_expired">, zod.ZodLiteral<"order_declined">, zod.ZodLiteral<"order_canceled">, zod.ZodLiteral<"order_expired">, zod.ZodLiteral<"provisioning_failed">, zod.ZodLiteral<null>]>>;
-        operation: zod.ZodUnion<readonly [zod.ZodObject<{
-            type: zod.ZodEnum<{
-                delete: "delete";
-                create: "create";
-                start: "start";
-                stop: "stop";
-                reboot: "reboot";
-                rebuild: "rebuild";
-                resize: "resize";
-                reset_password: "reset_password";
-                attach_disk: "attach_disk";
-                detach_disk: "detach_disk";
-                attach_port: "attach_port";
-                detach_port: "detach_port";
-                bind_floating_ip: "bind_floating_ip";
-                unbind_floating_ip: "unbind_floating_ip";
-                suspend: "suspend";
-                resume: "resume";
-            }>;
-            started_at: zod.z.ZodISODateTime;
-        }, zod.z.core.$strict>, zod.ZodNull]>;
-        order_id: zod.ZodNullable<zod.ZodUUID>;
-        order_item_id: zod.ZodNullable<zod.ZodUUID>;
-        checkout_session_id: zod.ZodNullable<zod.ZodUUID>;
-        subscription_id: zod.ZodNullable<zod.ZodUUID>;
-        release_subscription_ids: zod.ZodArray<zod.ZodUUID>;
-        release_set: zod.ZodArray<zod.ZodObject<{
-            subscription_id: zod.ZodUUID;
-            resource: zod.ZodObject<{
-                type: zod.ZodEnum<{
-                    image: "image";
-                    instance: "instance";
-                    disk: "disk";
-                    floating_ip: "floating_ip";
-                    backup_service: "backup_service";
-                    snapshot_quota: "snapshot_quota";
-                    backup_capacity_pack: "backup_capacity_pack";
-                }>;
-                id: zod.ZodUUID;
-                name: zod.ZodString;
-            }, zod.z.core.$strict>;
-        }, zod.z.core.$strict>>;
-        access_state: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"pending">, zod.ZodLiteral<"enabled">, zod.ZodLiteral<"suspended">, zod.ZodLiteral<"reclaimed">, zod.ZodLiteral<null>]>>;
-        source_disk_id: zod.ZodNullable<zod.ZodUUID>;
-    }, zod.z.core.$strict>>;
-    checkout_session_id: zod.ZodUUID;
-    order_id: zod.ZodNullable<zod.ZodUUID>;
-    password: zod.ZodNullable<zod.ZodString>;
-}, zod.z.core.$strict>;
-export type LaunchInstanceResponseBody = zod.input<typeof LaunchInstanceResponseBody>;
-export type LaunchInstanceResponseBodyOutput = zod.output<typeof LaunchInstanceResponseBody>;

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

@@ -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.
- * - **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 and rates from Billing with `search-prices`, 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.
- * - **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 { InstanceResource } from "./instanceResource.zod.js";
-export const launchInstanceResponseBodyInstancesMax = 20;
-export const LaunchInstanceResponseBody = zod
-    .strictObject({
-    instances: zod
-        .array(InstanceResource)
-        .min(1)
-        .max(launchInstanceResponseBodyInstancesMax)
-        .describe("One instance per requested instance, in request order. Their IDs stay the same through checkout and\ncreation."),
-    checkout_session_id: zod
-        .uuid()
-        .describe("The Billing Checkout Session of this purchase. With deferred checkout, the customer completes it in Billing."),
-    order_id: zod
-        .uuid()
-        .nullable()
-        .describe("The order created when checkout completes, at once for automatic checkout; null until then."),
-    password: zod
-        .string()
-        .nullable()
-        .describe("Generated login password, returned only by this response. Null when no password was generated."),
-})
-    .describe("The new instances, `pending` until their order is accepted, and the Checkout Session they share.");

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

@@ -1,34 +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.
- * - **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 and rates from Billing with `search-prices`, 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.
- * - **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 listAvailabilityZonesParamsPageDefault = 1;
-export declare const listAvailabilityZonesParamsPageMax = 2147483647;
-export declare const listAvailabilityZonesParamsPageSizeDefault = 50;
-export declare const listAvailabilityZonesParamsPageSizeMax = 200;
-export declare const ListAvailabilityZonesParams: zod.ZodObject<{
-    page: zod.ZodDefault<zod.ZodInt>;
-    page_size: zod.ZodDefault<zod.ZodInt>;
-}, zod.z.core.$strict>;
-export type ListAvailabilityZonesParams = zod.input<typeof ListAvailabilityZonesParams>;
-export type ListAvailabilityZonesParamsOutput = zod.output<typeof ListAvailabilityZonesParams>;

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

@@ -1,40 +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.
- * - **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 and rates from Billing with `search-prices`, 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.
- * - **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 const listAvailabilityZonesParamsPageDefault = 1;
-export const listAvailabilityZonesParamsPageMax = 2147483647;
-export const listAvailabilityZonesParamsPageSizeDefault = 50;
-export const listAvailabilityZonesParamsPageSizeMax = 200;
-export const ListAvailabilityZonesParams = zod.strictObject({
-    page: zod
-        .int()
-        .min(1)
-        .max(listAvailabilityZonesParamsPageMax)
-        .default(listAvailabilityZonesParamsPageDefault),
-    page_size: zod
-        .int()
-        .min(1)
-        .max(listAvailabilityZonesParamsPageSizeMax)
-        .default(listAvailabilityZonesParamsPageSizeDefault),
-});

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

@@ -1,34 +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.
- * - **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 and rates from Billing with `search-prices`, 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.
- * - **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 listBackupCapacityPacksParamsPageDefault = 1;
-export declare const listBackupCapacityPacksParamsPageMax = 2147483647;
-export declare const listBackupCapacityPacksParamsPageSizeDefault = 50;
-export declare const listBackupCapacityPacksParamsPageSizeMax = 200;
-export declare const ListBackupCapacityPacksParams: zod.ZodObject<{
-    page: zod.ZodDefault<zod.ZodInt>;
-    page_size: zod.ZodDefault<zod.ZodInt>;
-}, zod.z.core.$strict>;
-export type ListBackupCapacityPacksParams = zod.input<typeof ListBackupCapacityPacksParams>;
-export type ListBackupCapacityPacksParamsOutput = zod.output<typeof ListBackupCapacityPacksParams>;

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

@@ -1,40 +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.
- * - **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 and rates from Billing with `search-prices`, 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.
- * - **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 const listBackupCapacityPacksParamsPageDefault = 1;
-export const listBackupCapacityPacksParamsPageMax = 2147483647;
-export const listBackupCapacityPacksParamsPageSizeDefault = 50;
-export const listBackupCapacityPacksParamsPageSizeMax = 200;
-export const ListBackupCapacityPacksParams = zod.strictObject({
-    page: zod
-        .int()
-        .min(1)
-        .max(listBackupCapacityPacksParamsPageMax)
-        .default(listBackupCapacityPacksParamsPageDefault),
-    page_size: zod
-        .int()
-        .min(1)
-        .max(listBackupCapacityPacksParamsPageSizeMax)
-        .default(listBackupCapacityPacksParamsPageSizeDefault),
-});

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

@@ -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.
- * - **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 and rates from Billing with `search-prices`, 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.
- * - **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 listBackupsParamsPageDefault = 1;
-export declare const listBackupsParamsPageMax = 2147483647;
-export declare const listBackupsParamsPageSizeDefault = 50;
-export declare const listBackupsParamsPageSizeMax = 200;
-export declare const ListBackupsParams: zod.ZodObject<{
-    disk_id: zod.ZodOptional<zod.ZodUUID>;
-    page: zod.ZodDefault<zod.ZodInt>;
-    page_size: zod.ZodDefault<zod.ZodInt>;
-}, zod.z.core.$strict>;
-export type ListBackupsParams = zod.input<typeof ListBackupsParams>;
-export type ListBackupsParamsOutput = zod.output<typeof ListBackupsParams>;