@leaflow/sdk 0.0.0-dev.35.g30ba751 → 0.0.0-dev.352.g85966ed

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

@@ -0,0 +1,125 @@
+/**
+ * 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 { InstanceOperation } from "./instanceOperation.zod.js";
+import { InstanceRestriction } from "./instanceRestriction.zod.js";
+import { ReleaseSetItem } from "./releaseSetItem.zod.js";
+export const instanceResourceLabelsMaxOne = 63;
+export const instanceResourceLoginUsernameMax = 32;
+export const instanceResourceNotesMax = 4096;
+export const InstanceResource = zod.strictObject({
+    availability_zone_id: zod.uuid(),
+    created_at: zod.iso.datetime({ offset: true }),
+    hostname: zod.string().describe("Hostname inside the instance; equals the instance id"),
+    id: zod.uuid(),
+    image_id: zod
+        .uuid()
+        .nullable()
+        .describe("Non-empty when the instance was created from an image, public or private"),
+    instance_type_id: zod.uuid().describe("The instance type in effect, and the basis for billing"),
+    ipv6_address: zod
+        .string()
+        .nullable()
+        .describe("IPv6 address of the primary network interface. Assigned automatically once IPv6 is enabled on the private network"),
+    labels: zod
+        .record(zod.string(), zod.string().max(instanceResourceLabelsMaxOne))
+        .describe("Your own classification of this instance, as key-value pairs. Empty when never set"),
+    login_username: zod
+        .string()
+        .max(instanceResourceLoginUsernameMax)
+        .describe("The account to log in as over SSH. The password set at creation belongs to this account"),
+    name: zod.string(),
+    notes: zod
+        .string()
+        .max(instanceResourceNotesMax)
+        .describe("A free-text note about this instance. Empty when never set"),
+    private_ip: zod.string().nullable().describe("Private address of the instance"),
+    private_network_id: zod.uuid().nullable(),
+    public_ips: zod
+        .array(zod.string())
+        .nullable()
+        .describe("Floating IPv4 addresses bound to the primary network interface; an empty array when none are bound"),
+    region_id: zod.uuid(),
+    status: zod
+        .enum([
+        "pending",
+        "provisioning",
+        "active",
+        "stopped",
+        "paused",
+        "suspended",
+        "shelved",
+        "shelved_offloaded",
+        "rescued",
+        "deleted",
+        "failed",
+        "error",
+        "unknown",
+        "missing",
+    ])
+        .describe("`pending` until the order is accepted: no virtual machine exists and addresses are null. `provisioning` while the instance is created, then `active`. `failed` means the instance was not created; `failure_reason` states why. `missing` means the virtual machine no longer exists in the cloud. The other values are the state last observed in the cloud; an operation in progress appears in `operation`, not here."),
+    subnet_id: zod.uuid().nullable(),
+    updated_at: zod.iso.datetime({ offset: true }),
+    generation: zod.int().min(1),
+    observed_at: zod.iso.datetime({ offset: true }).nullable(),
+    restrictions: zod.array(InstanceRestriction),
+    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 instance is refunded."),
+    operation: zod
+        .union([InstanceOperation, zod.null()])
+        .describe("The operation in progress on this instance, or null when none is."),
+    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 subscriptions a cancellation through Billing has to cover to release this instance: its own and those of the disks deleted with it. Snapshots are cleaned up with their source disk without canceling the project's snapshot quota. Subscriptions that have ended are not listed, and the list is empty when no subscription pays for any of them."),
+    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(),
+    source_disk_id: zod
+        .uuid()
+        .nullable()
+        .describe("Non-empty when the instance was created from a disk you already had, instead of from an image"),
+});

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

@@ -0,0 +1,39 @@
+/**
+ * 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 instanceRestrictionSourceIdMax = 255;
+export declare const instanceRestrictionReasonCodeMax = 128;
+export declare const InstanceRestriction: 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>;
+export type InstanceRestriction = zod.input<typeof InstanceRestriction>;
+export type InstanceRestrictionOutput = zod.output<typeof InstanceRestriction>;

package/dist/compute/v1/generated/validators/instanceRestriction.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 instanceRestrictionSourceIdMax = 255;
+export const instanceRestrictionReasonCodeMax = 128;
+export const InstanceRestriction = zod
+    .strictObject({
+    id: zod.uuid(),
+    source: zod.enum(["billing", "iam", "operator"]),
+    source_id: zod.string().min(1).max(instanceRestrictionSourceIdMax),
+    reason_code: zod.string().min(1).max(instanceRestrictionReasonCodeMax),
+    created_at: zod.iso.datetime({ offset: true }),
+})
+    .describe("An independent restriction on use. Removing one restriction never removes another source’s restriction, and never starts an instance its user stopped.");

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

@@ -0,0 +1,74 @@
+/**
+ * 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 InstanceTypeListResponseBody: zod.ZodObject<{
+    items: zod.ZodArray<zod.ZodObject<{
+        availability_zone_id: zod.ZodUUID;
+        id: zod.ZodUUID;
+        max_bandwidth_mbps: zod.ZodInt;
+        network_egress_kbps: zod.ZodNullable<zod.ZodInt>;
+        network_ingress_kbps: zod.ZodNullable<zod.ZodInt>;
+        max_floating_ips: zod.ZodInt;
+        max_ports: zod.ZodInt;
+        name: zod.ZodString;
+        ram_mb: zod.ZodInt;
+        region_id: zod.ZodUUID;
+        vcpus: zod.ZodInt;
+        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 InstanceTypeListResponseBody = zod.input<typeof InstanceTypeListResponseBody>;
+export type InstanceTypeListResponseBodyOutput = zod.output<typeof InstanceTypeListResponseBody>;

package/dist/compute/v1/generated/validators/instanceTypeListResponseBody.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 { InstanceTypeResource } from "./instanceTypeResource.zod.js";
+import { OffsetPagination } from "./offsetPagination.zod.js";
+export const InstanceTypeListResponseBody = zod.strictObject({
+    items: zod.array(InstanceTypeResource),
+    pagination: OffsetPagination,
+});

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

@@ -0,0 +1,67 @@
+/**
+ * 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 InstanceTypeResource: zod.ZodObject<{
+    availability_zone_id: zod.ZodUUID;
+    id: zod.ZodUUID;
+    max_bandwidth_mbps: zod.ZodInt;
+    network_egress_kbps: zod.ZodNullable<zod.ZodInt>;
+    network_ingress_kbps: zod.ZodNullable<zod.ZodInt>;
+    max_floating_ips: zod.ZodInt;
+    max_ports: zod.ZodInt;
+    name: zod.ZodString;
+    ram_mb: zod.ZodInt;
+    region_id: zod.ZodUUID;
+    vcpus: zod.ZodInt;
+    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 InstanceTypeResource = zod.input<typeof InstanceTypeResource>;
+export type InstanceTypeResourceOutput = zod.output<typeof InstanceTypeResource>;

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

@@ -0,0 +1,49 @@
+/**
+ * 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 InstanceTypeResource = zod.strictObject({
+    availability_zone_id: zod.uuid(),
+    id: zod.uuid(),
+    max_bandwidth_mbps: zod
+        .int()
+        .describe("The most public bandwidth a machine of this type may be given, in Mbps. Asking for more\nwhen creating a machine, or raising a bound address past it, is refused.\n\nA ceiling on what can be bought, not a speed. How fast the machine's own interfaces run is\n`network_egress_kbps` / `network_ingress_kbps`."),
+    network_egress_kbps: zod
+        .int()
+        .nullable()
+        .describe("Outbound ceiling of **each** network interface, in kbps. Null when this type is not\nrate-limited.\n\nPer interface rather than per machine: a machine with two interfaces has this ceiling on\neach of them, not shared between them. `max_ports` says how many it may have."),
+    network_ingress_kbps: zod
+        .int()
+        .nullable()
+        .describe("Inbound ceiling of each network interface, in kbps. Null when this type is not rate-limited"),
+    max_floating_ips: zod.int(),
+    max_ports: zod.int(),
+    name: zod.string(),
+    ram_mb: zod.int(),
+    region_id: zod.uuid(),
+    vcpus: zod.int(),
+    pricing: zod
+        .union([Pricing, zod.null()])
+        .describe("How an instance of this type can be bought, per instance. Null when the project has no billing account."),
+});

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

@@ -0,0 +1,113 @@
+/**
+ * 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 launchInstanceQuoteRequestBodyCountDefault = 1;
+export declare const launchInstanceQuoteRequestBodyCountMax = 20;
+export declare const launchInstanceQuoteRequestBodyNameMax = 128;
+export declare const launchInstanceQuoteRequestBodyPasswordMax = 128;
+export declare const LaunchInstanceQuoteRequestBody: zod.ZodObject<{
+    floating_ip_id: zod.ZodOptional<zod.ZodUUID>;
+    count: zod.ZodDefault<zod.ZodInt>;
+    generate_password: zod.ZodOptional<zod.ZodBoolean>;
+    compute: zod.ZodObject<{
+        instance_type_id: zod.ZodUUID;
+        billing: zod.ZodObject<{
+            mode: zod.ZodEnum<{
+                postpaid: "postpaid";
+                prepaid: "prepaid";
+            }>;
+            period: zod.ZodOptional<zod.ZodObject<{
+                unit: zod.ZodEnum<{
+                    month: "month";
+                    year: "year";
+                }>;
+                count: zod.ZodInt;
+            }, zod.z.core.$strict>>;
+            termination_policy: zod.ZodOptional<zod.ZodEnum<{
+                immediate: "immediate";
+                period_end: "period_end";
+            }>>;
+        }, zod.z.core.$strict>;
+    }, zod.z.core.$strict>;
+    name: zod.ZodString;
+    password: zod.ZodOptional<zod.ZodString>;
+    port_id: zod.ZodOptional<zod.ZodUUID>;
+    security_group_ids: zod.ZodOptional<zod.ZodNullable<zod.ZodArray<zod.ZodUUID>>>;
+    subnet_id: zod.ZodOptional<zod.ZodUUID>;
+    boot_disk: zod.ZodDiscriminatedUnion<[zod.ZodObject<{
+        type: zod.ZodEnum<{
+            image: "image";
+        }>;
+        image_id: zod.ZodUUID;
+        disk_type_id: zod.ZodUUID;
+        size_gb: zod.ZodInt;
+        delete_with_instance: zod.ZodDefault<zod.ZodBoolean>;
+        billing: zod.ZodObject<{
+            mode: zod.ZodEnum<{
+                postpaid: "postpaid";
+                prepaid: "prepaid";
+            }>;
+            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<{
+            mode: zod.ZodEnum<{
+                postpaid: "postpaid";
+                prepaid: "prepaid";
+            }>;
+            period: zod.ZodOptional<zod.ZodObject<{
+                unit: zod.ZodEnum<{
+                    month: "month";
+                    year: "year";
+                }>;
+                count: zod.ZodInt;
+            }, zod.z.core.$strict>>;
+            termination_policy: zod.ZodOptional<zod.ZodEnum<{
+                immediate: "immediate";
+                period_end: "period_end";
+            }>>;
+        }, zod.z.core.$strict>;
+    }, zod.z.core.$strict>>;
+}, zod.z.core.$strict>;
+export type LaunchInstanceQuoteRequestBody = zod.input<typeof LaunchInstanceQuoteRequestBody>;
+export type LaunchInstanceQuoteRequestBodyOutput = zod.output<typeof LaunchInstanceQuoteRequestBody>;