@leaflow/sdk 0.105.0 → 0.107.0

package/dist/gen/compute/v1/validators/floatingIPResource.zod.d.ts

@@ -0,0 +1,94 @@
+/**
+ * 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 a PlacedOrder. They are readable at once and start as `pending`: 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 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 order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid 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.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; 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` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **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 order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records 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 FloatingIPResource: zod.ZodObject<{
+    address: zod.ZodNullable<zod.ZodString>;
+    bandwidth_mbps: zod.ZodNullable<zod.ZodInt>;
+    created_at: zod.z.ZodISODateTime;
+    id: zod.ZodUUID;
+    region_id: zod.ZodUUID;
+    status: zod.ZodEnum<{
+        error: "error";
+        unknown: "unknown";
+        pending: "pending";
+        failed: "failed";
+        deleted: "deleted";
+        provisioning: "provisioning";
+        available: "available";
+        missing: "missing";
+    }>;
+    order_id: zod.ZodNullable<zod.ZodUUID>;
+    order_item_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>]>>;
+    failure_reason: zod.ZodNullable<zod.ZodUnion<readonly [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<{
+            create: "create";
+            bind: "bind";
+            unbind: "unbind";
+            set_bandwidth: "set_bandwidth";
+            suspend: "suspend";
+            resume: "resume";
+            delete: "delete";
+        }>;
+        started_at: zod.z.ZodISODateTime;
+    }, zod.z.core.$strict>, zod.ZodNull]>;
+    generation: zod.ZodInt;
+    observed_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    binding: zod.ZodUnion<readonly [zod.ZodObject<{
+        id: zod.ZodUUID;
+        ipv4_allocation_id: zod.ZodUUID;
+        port_address_id: zod.ZodUUID;
+        address: zod.ZodString;
+        fixed_ip: zod.ZodString;
+        state: zod.ZodEnum<{
+            unknown: "unknown";
+            bound: "bound";
+            released: "released";
+        }>;
+        bound_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+        unbound_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+        released_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    }, zod.z.core.$strict>, zod.ZodNull]>;
+}, zod.z.core.$strict>;
+export type FloatingIPResource = zod.input<typeof FloatingIPResource>;
+export type FloatingIPResourceOutput = zod.output<typeof FloatingIPResource>;

package/dist/gen/compute/v1/validators/floatingIPResource.zod.js

@@ -0,0 +1,88 @@
+/**
+ * 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 a PlacedOrder. They are readable at once and start as `pending`: 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 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 order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid 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.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; 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` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **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 order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records 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 { FloatingIPOperation } from "./floatingIPOperation.zod.js";
+import { IPv4Binding } from "./iPv4Binding.zod.js";
+import { ReleaseSetItem } from "./releaseSetItem.zod.js";
+export const FloatingIPResource = zod
+    .strictObject({
+    address: zod
+        .string()
+        .nullable()
+        .describe("The allocated public address. Null until the address is allocated."),
+    bandwidth_mbps: zod.int().nullable(),
+    created_at: zod.iso.datetime({ offset: true }),
+    id: zod.uuid(),
+    region_id: zod.uuid(),
+    status: zod
+        .enum([
+        "pending",
+        "provisioning",
+        "available",
+        "deleted",
+        "failed",
+        "error",
+        "unknown",
+        "missing",
+    ])
+        .describe("`pending` until the order is accepted, with no address allocated; `provisioning` while the address is allocated; then `available`. `failed` means no address was allocated; `failure_reason` states why. `missing` means the address no longer exists in the cloud."),
+    order_id: zod.uuid().nullable(),
+    order_item_id: zod.uuid().nullable().describe("The Billing order item for this resource."),
+    subscription_id: zod
+        .uuid()
+        .nullable()
+        .describe("The Billing subscription associated with this resource. It may still be pending; its\npresence does not imply delivery or metering. Null when no subscription is associated."),
+    release_subscription_ids: zod
+        .array(zod.uuid())
+        .describe("The subscription a cancellation through Billing has to cover to release this floating IP. A subscription that has ended is not listed, and the list is empty when no subscription pays for the floating IP."),
+    release_set: zod
+        .array(ReleaseSetItem)
+        .describe("The subscriptions of `release_subscription_ids`, in the same order, each with the resource it pays for, so that each line of a cancellation can name what it releases."),
+    access_state: zod
+        .union([
+        zod.literal("pending"),
+        zod.literal("enabled"),
+        zod.literal("suspended"),
+        zod.literal("reclaimed"),
+        zod.literal(null),
+    ])
+        .nullable(),
+    failure_reason: zod
+        .union([
+        zod.literal("order_declined"),
+        zod.literal("order_canceled"),
+        zod.literal("order_expired"),
+        zod.literal("provisioning_failed"),
+        zod.literal(null),
+    ])
+        .nullable()
+        .describe("Why creation failed; null unless `status` is `failed`. `provisioning_failed` means creation failed after the order was accepted, and the charge for this floating IP is refunded."),
+    operation: zod
+        .union([FloatingIPOperation, zod.null()])
+        .describe("The operation in progress on this floating IP, or null when none is."),
+    generation: zod.int().min(1),
+    observed_at: zod.iso.datetime({ offset: true }).nullable(),
+    binding: zod.union([IPv4Binding, zod.null()]),
+})
+    .describe("One purchased public IP resource, including its bandwidth configuration. Bandwidth has no\nseparate Compute resource ID; one subscription pays for the address and its bandwidth.\nChanging bandwidth updates this same resource, not another allocation.");

package/dist/gen/compute/v1/validators/getInstanceConsoleOutputParams.zod.d.ts

@@ -0,0 +1,32 @@
+/**
+ * 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 a PlacedOrder. They are readable at once and start as `pending`: 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 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 order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid 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.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; 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` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **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 order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records 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 getInstanceConsoleOutputParamsLinesDefault = 200;
+export declare const getInstanceConsoleOutputParamsLinesMin = 0;
+export declare const getInstanceConsoleOutputParamsLinesMax = 10000;
+export declare const GetInstanceConsoleOutputParams: zod.ZodObject<{
+    lines: zod.ZodDefault<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type GetInstanceConsoleOutputParams = zod.input<typeof GetInstanceConsoleOutputParams>;
+export type GetInstanceConsoleOutputParamsOutput = zod.output<typeof GetInstanceConsoleOutputParams>;

package/dist/gen/compute/v1/validators/getInstanceConsoleOutputParams.zod.js

@@ -0,0 +1,35 @@
+/**
+ * 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 a PlacedOrder. They are readable at once and start as `pending`: 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 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 order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid 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.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; 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` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **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 order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records 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 getInstanceConsoleOutputParamsLinesDefault = 200;
+export const getInstanceConsoleOutputParamsLinesMin = 0;
+export const getInstanceConsoleOutputParamsLinesMax = 10000;
+export const GetInstanceConsoleOutputParams = zod.strictObject({
+    lines: zod
+        .int()
+        .min(getInstanceConsoleOutputParamsLinesMin)
+        .max(getInstanceConsoleOutputParamsLinesMax)
+        .default(getInstanceConsoleOutputParamsLinesDefault)
+        .describe("Number of trailing lines to return; 0 returns the entire output"),
+});

package/dist/gen/compute/v1/validators/iPv4Binding.zod.d.ts

@@ -0,0 +1,41 @@
+/**
+ * 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 a PlacedOrder. They are readable at once and start as `pending`: 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 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 order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid 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.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; 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` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **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 order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records 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 IPv4Binding: zod.ZodObject<{
+    id: zod.ZodUUID;
+    ipv4_allocation_id: zod.ZodUUID;
+    port_address_id: zod.ZodUUID;
+    address: zod.ZodString;
+    fixed_ip: zod.ZodString;
+    state: zod.ZodEnum<{
+        unknown: "unknown";
+        bound: "bound";
+        released: "released";
+    }>;
+    bound_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    unbound_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    released_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+}, zod.z.core.$strict>;
+export type IPv4Binding = zod.input<typeof IPv4Binding>;
+export type IPv4BindingOutput = zod.output<typeof IPv4Binding>;

package/dist/gen/compute/v1/validators/iPv4Binding.zod.js

@@ -0,0 +1,35 @@
+/**
+ * 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 a PlacedOrder. They are readable at once and start as `pending`: 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 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 order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid 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.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; 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` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **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 order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records 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 IPv4Binding = zod.strictObject({
+    id: zod.uuid(),
+    ipv4_allocation_id: zod.uuid(),
+    port_address_id: zod.uuid(),
+    address: zod.string(),
+    fixed_ip: zod.string(),
+    state: zod.enum(["bound", "released", "unknown"]),
+    bound_at: zod.iso.datetime({ offset: true }).nullable(),
+    unbound_at: zod.iso.datetime({ offset: true }).nullable(),
+    released_at: zod.iso.datetime({ offset: true }).nullable(),
+});

package/dist/gen/compute/v1/validators/iPv4PoolListResponseBody.zod.d.ts

@@ -0,0 +1,94 @@
+/**
+ * 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 a PlacedOrder. They are readable at once and start as `pending`: 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 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 order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid 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.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; 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` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **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 order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records 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 IPv4PoolListResponseBody: zod.ZodObject<{
+    items: zod.ZodArray<zod.ZodObject<{
+        id: zod.ZodUUID;
+        region_id: zod.ZodUUID;
+        name: zod.ZodString;
+        pricing: zod.ZodUnion<readonly [zod.ZodObject<{
+            currency: zod.ZodString;
+            options: zod.ZodArray<zod.ZodObject<{
+                mode: zod.ZodEnum<{
+                    postpaid: "postpaid";
+                    prepaid: "prepaid";
+                }>;
+                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>, zod.ZodNull]>;
+        bandwidth_pricing: zod.ZodUnion<readonly [zod.ZodObject<{
+            currency: zod.ZodString;
+            options: zod.ZodArray<zod.ZodObject<{
+                mode: zod.ZodEnum<{
+                    postpaid: "postpaid";
+                    prepaid: "prepaid";
+                }>;
+                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>, zod.ZodNull]>;
+    }, zod.z.core.$strict>>;
+    pagination: zod.ZodObject<{
+        page: zod.ZodInt;
+        page_size: zod.ZodInt;
+        total_count: zod.ZodOptional<zod.ZodInt>;
+    }, zod.z.core.$strict>;
+}, zod.z.core.$strict>;
+export type IPv4PoolListResponseBody = zod.input<typeof IPv4PoolListResponseBody>;
+export type IPv4PoolListResponseBodyOutput = zod.output<typeof IPv4PoolListResponseBody>;

package/dist/gen/compute/v1/validators/iPv4PoolListResponseBody.zod.js

@@ -0,0 +1,30 @@
+/**
+ * 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 a PlacedOrder. They are readable at once and start as `pending`: 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 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 order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid 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.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; 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` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **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 order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records 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 { IPv4PoolResource } from "./iPv4PoolResource.zod.js";
+import { OffsetPagination } from "./offsetPagination.zod.js";
+export const IPv4PoolListResponseBody = zod.strictObject({
+    items: zod.array(IPv4PoolResource),
+    pagination: OffsetPagination,
+});

package/dist/gen/compute/v1/validators/iPv4PoolResource.zod.d.ts

@@ -0,0 +1,87 @@
+/**
+ * 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 a PlacedOrder. They are readable at once and start as `pending`: 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 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 order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid 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.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; 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` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **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 order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records 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 IPv4PoolResource: zod.ZodObject<{
+    id: zod.ZodUUID;
+    region_id: zod.ZodUUID;
+    name: zod.ZodString;
+    pricing: zod.ZodUnion<readonly [zod.ZodObject<{
+        currency: zod.ZodString;
+        options: zod.ZodArray<zod.ZodObject<{
+            mode: zod.ZodEnum<{
+                postpaid: "postpaid";
+                prepaid: "prepaid";
+            }>;
+            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>, zod.ZodNull]>;
+    bandwidth_pricing: zod.ZodUnion<readonly [zod.ZodObject<{
+        currency: zod.ZodString;
+        options: zod.ZodArray<zod.ZodObject<{
+            mode: zod.ZodEnum<{
+                postpaid: "postpaid";
+                prepaid: "prepaid";
+            }>;
+            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>, zod.ZodNull]>;
+}, zod.z.core.$strict>;
+export type IPv4PoolResource = zod.input<typeof IPv4PoolResource>;
+export type IPv4PoolResourceOutput = zod.output<typeof IPv4PoolResource>;

package/dist/gen/compute/v1/validators/iPv4PoolResource.zod.js

@@ -0,0 +1,36 @@
+/**
+ * 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 a PlacedOrder. They are readable at once and start as `pending`: 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 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 order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid 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.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; 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` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **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 order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records 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 { Pricing } from "./pricing.zod.js";
+export const IPv4PoolResource = zod.strictObject({
+    id: zod.uuid(),
+    region_id: zod.uuid(),
+    name: zod.string(),
+    pricing: zod
+        .union([Pricing, zod.null()])
+        .describe("How an address from this pool can be bought, per address. Null when the project has no billing account."),
+    bandwidth_pricing: zod
+        .union([Pricing, zod.null()])
+        .describe("How the bandwidth of an address from this pool is billed, per Mbit/s. It is bought in the same purchase as the address, with the same billing choice. Null when the project has no billing account."),
+});