@leaflow/sdk 0.121.0 → 0.123.0

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

@@ -117,8 +117,30 @@ export declare const LaunchInstanceResponseBody: zod.ZodObject<{
         source_disk_id: zod.ZodNullable<zod.ZodUUID>;
     }, zod.z.core.$strict>>;
     order: zod.ZodObject<{
-        invoice_id: zod.ZodNullable<zod.ZodUUID>;
         order_id: zod.ZodUUID;
+        invoice_id: zod.ZodUUID;
+        invoice: zod.ZodObject<{
+            id: zod.ZodUUID;
+            number: zod.ZodOptional<zod.ZodString>;
+            currency: zod.ZodString;
+            status: zod.ZodEnum<{
+                void: "void";
+                open: "open";
+                draft: "draft";
+                paid: "paid";
+                uncollectible: "uncollectible";
+            }>;
+            subtotal: zod.ZodString;
+            discount_amount: zod.ZodString;
+            tax_amount: zod.ZodString;
+            total: zod.ZodString;
+            amount_paid: zod.ZodString;
+            pre_payment_credit_notes_amount: zod.ZodString;
+            post_payment_credit_notes_amount: zod.ZodString;
+            amount_due: zod.ZodString;
+            amount_refunded: zod.ZodString;
+            due_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+        }, zod.z.core.$strict>;
     }, zod.z.core.$strict>;
     password: zod.ZodNullable<zod.ZodString>;
 }, zod.z.core.$strict>;

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

@@ -0,0 +1,31 @@
+/**
+ * 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 namedIdentityNameMax = 255;
+export declare const NamedIdentity: zod.ZodObject<{
+    id: zod.ZodUUID;
+    name: zod.ZodString;
+}, zod.z.core.$strict>;
+export type NamedIdentity = zod.input<typeof NamedIdentity>;
+export type NamedIdentityOutput = zod.output<typeof NamedIdentity>;

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

@@ -0,0 +1,31 @@
+/**
+ * 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 namedIdentityNameMax = 255;
+export const NamedIdentity = zod
+    .strictObject({
+    id: zod.uuid(),
+    name: zod.string().max(namedIdentityNameMax),
+})
+    .describe("Which object this is, together with what a person currently calls it.\n\nThe name is for display. It is chosen by whoever owns the object, it changes, it is not unique\nbetween objects, and it may be empty when nobody has named it yet — so it must not be used to\naddress, match or deduplicate anything. Addressing is by id.\n\nThis differs from an identity carrying a lookup key: a lookup key is written once by an operator,\nis unique, and can be used to fetch the object. A name cannot.");

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

@@ -0,0 +1,31 @@
+/**
+ * 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 ObjectIdentity: zod.ZodObject<{
+    lookup_key: zod.ZodOptional<zod.ZodString>;
+    id: zod.ZodUUID;
+    name: zod.ZodString;
+}, zod.z.core.$strict>;
+export type ObjectIdentity = zod.input<typeof ObjectIdentity>;
+export type ObjectIdentityOutput = zod.output<typeof ObjectIdentity>;

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

@@ -0,0 +1,31 @@
+/**
+ * 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 ObjectIdentity = zod
+    .strictObject({
+    lookup_key: zod.string().optional(),
+    id: zod.uuid(),
+    name: zod.string(),
+})
+    .describe("A catalog object inlined for display.");

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

@@ -0,0 +1,159 @@
+/**
+ * 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 Order: zod.ZodObject<{
+    coupon_id: zod.ZodOptional<zod.ZodUUID>;
+    coupon: zod.ZodOptional<zod.ZodObject<{
+        lookup_key: zod.ZodOptional<zod.ZodString>;
+        id: zod.ZodUUID;
+        name: zod.ZodString;
+    }, zod.z.core.$strict>>;
+    promotion_code_id: zod.ZodOptional<zod.ZodUUID>;
+    promotion_code: zod.ZodOptional<zod.ZodString>;
+    invoice_id: zod.ZodUUID;
+    invoice: zod.ZodObject<{
+        id: zod.ZodUUID;
+        number: zod.ZodOptional<zod.ZodString>;
+        currency: zod.ZodString;
+        status: zod.ZodEnum<{
+            void: "void";
+            open: "open";
+            draft: "draft";
+            paid: "paid";
+            uncollectible: "uncollectible";
+        }>;
+        subtotal: zod.ZodString;
+        discount_amount: zod.ZodString;
+        tax_amount: zod.ZodString;
+        total: zod.ZodString;
+        amount_paid: zod.ZodString;
+        pre_payment_credit_notes_amount: zod.ZodString;
+        post_payment_credit_notes_amount: zod.ZodString;
+        amount_due: zod.ZodString;
+        amount_refunded: zod.ZodString;
+        due_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+    }, zod.z.core.$strict>;
+    paid_with: zod.ZodOptional<zod.ZodObject<{
+        method_type: zod.ZodString;
+        payment_gateway: zod.ZodOptional<zod.ZodString>;
+        payment_method_id: zod.ZodOptional<zod.ZodUUID>;
+        brand: zod.ZodOptional<zod.ZodString>;
+        last4: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>>;
+    account: zod.ZodOptional<zod.ZodObject<{
+        id: zod.ZodInt;
+        name: zod.ZodString;
+        currency: zod.ZodString;
+    }, zod.z.core.$strict>>;
+    change_effective_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+    id: zod.ZodUUID;
+    project_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
+    project: zod.ZodOptional<zod.ZodUnion<readonly [zod.ZodObject<{
+        id: zod.ZodUUID;
+        name: zod.ZodString;
+    }, zod.z.core.$strict>, zod.ZodNull]>>;
+    billing_account_id: zod.ZodOptional<zod.ZodInt>;
+    currency: zod.ZodString;
+    type: zod.ZodEnum<{
+        new: "new";
+        renew: "renew";
+        modify: "modify";
+    }>;
+    status: zod.ZodEnum<{
+        pending: "pending";
+        completed: "completed";
+        failed: "failed";
+        canceled: "canceled";
+        accepted: "accepted";
+        partially_completed: "partially_completed";
+    }>;
+    change_effective: zod.ZodOptional<zod.ZodEnum<{
+        none: "none";
+        immediate: "immediate";
+        period_end: "period_end";
+    }>>;
+    expires_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+    checkout_confirmed_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+    created_at: zod.z.ZodISODateTime;
+    items: zod.ZodArray<zod.ZodObject<{
+        invoice_item_ids: zod.ZodOptional<zod.ZodArray<zod.ZodUUID>>;
+        position: zod.ZodOptional<zod.ZodInt>;
+        configuration: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
+        subscription_id: zod.ZodOptional<zod.ZodUUID>;
+        interval: zod.ZodEnum<{
+            none: "none";
+            day: "day";
+            month: "month";
+            year: "year";
+        }>;
+        interval_count: zod.ZodOptional<zod.ZodInt>;
+        termination_policy: zod.ZodOptional<zod.ZodEnum<{
+            immediate: "immediate";
+            period_end: "period_end";
+        }>>;
+        refund_policy: zod.ZodOptional<zod.ZodEnum<{
+            none: "none";
+            prorated: "prorated";
+        }>>;
+        refund_monthly_amount: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
+        refund_hourly_amount: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
+        completes_on_payment: zod.ZodBoolean;
+        recurring_amount: zod.ZodOptional<zod.ZodString>;
+        setup_amount: zod.ZodOptional<zod.ZodString>;
+        charge_type: zod.ZodEnum<{
+            postpaid: "postpaid";
+            prepaid: "prepaid";
+            one_time: "one_time";
+        }>;
+        tax_amount: zod.ZodOptional<zod.ZodString>;
+        tax_included_amount: zod.ZodOptional<zod.ZodString>;
+        id: zod.ZodUUID;
+        order_id: zod.ZodOptional<zod.ZodUUID>;
+        price_id: zod.ZodUUID;
+        product_id: zod.ZodOptional<zod.ZodString>;
+        product: zod.ZodOptional<zod.ZodObject<{
+            id: zod.ZodString;
+            name: zod.ZodString;
+            description: zod.ZodOptional<zod.ZodString>;
+        }, zod.z.core.$strict>>;
+        plan_id: zod.ZodUUID;
+        plan_name: zod.ZodString;
+        quantity: zod.ZodString;
+        unit_amount: zod.ZodOptional<zod.ZodString>;
+        gross_amount: zod.ZodOptional<zod.ZodString>;
+        discount_amount: zod.ZodOptional<zod.ZodString>;
+        amount: zod.ZodOptional<zod.ZodString>;
+        currency: zod.ZodString;
+        period_start: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+        period_end: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+        status: zod.ZodEnum<{
+            pending: "pending";
+            completed: "completed";
+            failed: "failed";
+            canceled: "canceled";
+        }>;
+    }, zod.z.core.$strict>>;
+}, zod.z.core.$strict>;
+export type Order = zod.input<typeof Order>;
+export type OrderOutput = zod.output<typeof Order>;

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

@@ -0,0 +1,81 @@
+/**
+ * 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 { AccountIdentity } from "./accountIdentity.zod.js";
+import { InvoiceSummary } from "./invoiceSummary.zod.js";
+import { NamedIdentity } from "./namedIdentity.zod.js";
+import { ObjectIdentity } from "./objectIdentity.zod.js";
+import { OrderItem } from "./orderItem.zod.js";
+import { OrderStatus } from "./orderStatus.zod.js";
+import { PaidWith } from "./paidWith.zod.js";
+export const Order = zod
+    .strictObject({
+    coupon_id: zod.uuid().optional(),
+    coupon: ObjectIdentity.optional(),
+    promotion_code_id: zod.uuid().optional(),
+    promotion_code: zod
+        .string()
+        .optional()
+        .describe("Code text frozen when the coupon was applied. Absent for an account discount."),
+    invoice_id: zod.uuid().describe("The order's invoice, the same as invoice.id."),
+    invoice: InvoiceSummary,
+    paid_with: PaidWith.optional().describe("How the order was paid. Absent until it is paid."),
+    account: AccountIdentity.optional(),
+    change_effective_at: zod.iso.datetime({ offset: true }).optional(),
+    id: zod.uuid(),
+    project_id: zod
+        .uuid()
+        .nullish()
+        .describe("Which project it was bought for. Absent for a purchase made at account level, such\nas a membership."),
+    project: zod
+        .union([NamedIdentity, zod.null()])
+        .optional()
+        .describe("The project and its current name, for display. Absent for a purchase at account level,\nand when the project no longer exists or its details cannot be read at the moment;\n`project_id` still identifies it then."),
+    billing_account_id: zod
+        .int()
+        .optional()
+        .describe("The billing account the order was placed with. It does not change when the project is later\nlinked to another billing account. While this account is suspended or closed the order cannot\nbe accepted, and the invoice of a change scheduled for the end of a period is not issued and the change is called off\nwhen the current period ends; such requests fail with BILLING_ACCOUNT_UNAVAILABLE."),
+    currency: zod.string(),
+    type: zod
+        .enum(["new", "renew", "modify"])
+        .describe("`new` buys, `renew` extends a prepaid subscription, `modify` changes a subscription's configuration or billing terms."),
+    status: OrderStatus,
+    change_effective: zod
+        .enum(["none", "immediate", "period_end"])
+        .optional()
+        .describe("When a plan change takes effect. `none` on anything that is not a change.\n\n`period_end` orders stay pending until the first period at the new price is paid. That period\nis invoiced shortly before the current paid period ends and starts when it ends; if the\ninvoice is still unpaid by then, the order is canceled and the subscription renews or ends as\nusual. Renewing in the meantime moves all of this along with it."),
+    expires_at: zod.iso
+        .datetime({ offset: true })
+        .nullish()
+        .describe("Acceptance deadline. Pending orders can expire automatically."),
+    checkout_confirmed_at: zod.iso
+        .datetime({ offset: true })
+        .nullish()
+        .describe("When the discount and amount were fixed: at placement for automatic checkout and for a\nzero total, otherwise when the invoice was first paid. Null while a deferred order awaits payment."),
+    created_at: zod.iso.datetime({ offset: true }),
+    items: zod
+        .array(OrderItem)
+        .describe("What was bought. Present on a single order and on every order in a list, so a list\ncan be rendered without a further request per row."),
+})
+    .describe("A recorded purchase with its invoice from placement; a zero-total invoice, such as for postpaid\nadmission, is issued and paid at placement whatever the checkout mode. Until checkout_confirmed_at is set, the\ninvoice is a draft at base prices: paying it fixes the discount and amount, issues it and collects it, and the\norder cannot be accepted before then. Coupon fields describe the discount fixed at that point and are absent\nbefore it; a quote never populates them. Payment and acceptance remain separate from resource delivery.");

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

@@ -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";
+export declare const orderCancelOrderItemIdsMax = 100;
+export declare const OrderCancel: zod.ZodObject<{
+    order_item_ids: zod.ZodOptional<zod.ZodArray<zod.ZodUUID>>;
+}, zod.z.core.$strict>;
+export type OrderCancel = zod.input<typeof OrderCancel>;
+export type OrderCancelOutput = zod.output<typeof OrderCancel>;

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

@@ -0,0 +1,33 @@
+/**
+ * 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 orderCancelOrderItemIdsMax = 100;
+export const OrderCancel = zod.strictObject({
+    order_item_ids: zod
+        .array(zod.uuid())
+        .min(1)
+        .max(orderCancelOrderItemIdsMax)
+        .optional()
+        .describe("Omit to select all still-pending items. Explicit selections name one or more items of this order; successful items cannot be reversed here."),
+});

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

@@ -0,0 +1,85 @@
+/**
+ * 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 orderItemPositionMin = 0;
+export declare const OrderItem: zod.ZodObject<{
+    invoice_item_ids: zod.ZodOptional<zod.ZodArray<zod.ZodUUID>>;
+    position: zod.ZodOptional<zod.ZodInt>;
+    configuration: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
+    subscription_id: zod.ZodOptional<zod.ZodUUID>;
+    interval: zod.ZodEnum<{
+        none: "none";
+        day: "day";
+        month: "month";
+        year: "year";
+    }>;
+    interval_count: zod.ZodOptional<zod.ZodInt>;
+    termination_policy: zod.ZodOptional<zod.ZodEnum<{
+        immediate: "immediate";
+        period_end: "period_end";
+    }>>;
+    refund_policy: zod.ZodOptional<zod.ZodEnum<{
+        none: "none";
+        prorated: "prorated";
+    }>>;
+    refund_monthly_amount: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
+    refund_hourly_amount: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
+    completes_on_payment: zod.ZodBoolean;
+    recurring_amount: zod.ZodOptional<zod.ZodString>;
+    setup_amount: zod.ZodOptional<zod.ZodString>;
+    charge_type: zod.ZodEnum<{
+        postpaid: "postpaid";
+        prepaid: "prepaid";
+        one_time: "one_time";
+    }>;
+    tax_amount: zod.ZodOptional<zod.ZodString>;
+    tax_included_amount: zod.ZodOptional<zod.ZodString>;
+    id: zod.ZodUUID;
+    order_id: zod.ZodOptional<zod.ZodUUID>;
+    price_id: zod.ZodUUID;
+    product_id: zod.ZodOptional<zod.ZodString>;
+    product: zod.ZodOptional<zod.ZodObject<{
+        id: zod.ZodString;
+        name: zod.ZodString;
+        description: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>>;
+    plan_id: zod.ZodUUID;
+    plan_name: zod.ZodString;
+    quantity: zod.ZodString;
+    unit_amount: zod.ZodOptional<zod.ZodString>;
+    gross_amount: zod.ZodOptional<zod.ZodString>;
+    discount_amount: zod.ZodOptional<zod.ZodString>;
+    amount: zod.ZodOptional<zod.ZodString>;
+    currency: zod.ZodString;
+    period_start: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+    period_end: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+    status: zod.ZodEnum<{
+        pending: "pending";
+        completed: "completed";
+        failed: "failed";
+        canceled: "canceled";
+    }>;
+}, zod.z.core.$strict>;
+export type OrderItem = zod.input<typeof OrderItem>;
+export type OrderItemOutput = zod.output<typeof OrderItem>;