@leaflow/sdk 0.0.0-dev.31.ge5a1cab → 0.0.0-dev.312.g59da4a6

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

@@ -0,0 +1,40 @@
+/**
+ * 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 OperationLogResource: zod.ZodObject<{
+    action: zod.ZodString;
+    actor: zod.ZodNullable<zod.ZodString>;
+    actor_name: zod.ZodNullable<zod.ZodString>;
+    by_platform: zod.ZodBoolean;
+    created_at: zod.z.ZodISODateTime;
+    failure: zod.ZodNullable<zod.ZodString>;
+    id: zod.ZodUUID;
+    payload: zod.ZodRecord<zod.ZodString, zod.ZodUnknown>;
+    region_id: zod.ZodNullable<zod.ZodUUID>;
+    subject_id: zod.ZodString;
+    subject_type: zod.ZodString;
+    succeeded: zod.ZodBoolean;
+}, zod.z.core.$strict>;
+export type OperationLogResource = zod.input<typeof OperationLogResource>;
+export type OperationLogResourceOutput = zod.output<typeof OperationLogResource>;

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

@@ -0,0 +1,48 @@
+/**
+ * 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 OperationLogResource = zod.strictObject({
+    action: zod.string().describe("Name of the operation; matches the operation id of the endpoint"),
+    actor: zod
+        .string()
+        .nullable()
+        .describe("The user who initiated the operation. Empty when the platform performed it"),
+    actor_name: zod
+        .string()
+        .nullable()
+        .describe("The name this user went by at the time of the operation, recorded alongside the operation itself. It is not refreshed afterwards: the record states who acted then, and a name read today is a statement about a different moment.\n\nNull on entries recorded before this field existed, and on entries performed by the platform. An empty string means the account had no name recorded."),
+    by_platform: zod.boolean().describe("True when the operation was performed by the platform"),
+    created_at: zod.iso.datetime({ offset: true }),
+    failure: zod.string().nullable().describe("Brief reason for the failure"),
+    id: zod.uuid(),
+    payload: zod
+        .record(zod.string(), zod.unknown())
+        .describe("Path and query parameters of the request. Fields such as passwords are redacted"),
+    region_id: zod.uuid().nullable(),
+    subject_id: zod
+        .string()
+        .describe("Empty for create operations: the id of the new resource is in the response, not in the request path"),
+    subject_type: zod.string(),
+    succeeded: zod.boolean(),
+});

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

@@ -0,0 +1,158 @@
+/**
+ * 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>>;
+        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,84 @@
+/**
+ * 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>>;
+    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>;

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

@@ -0,0 +1,88 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Compute API
+ * Leaflow Compute user API for managing instances, disks, snapshots, backups, images, private networks, subnets, routes, security groups, network interfaces and floating IPs.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `scopedTokenAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **Purchases.** A purchase that creates resources returns them together with a PlacedOrder. They are readable at once and start as `pending`: the order has not been accepted, nothing exists in the cloud, no inventory such as an address is held, and fields known only after allocation, such as addresses, are null. Once Billing accepts the order, a resource becomes `provisioning` and then reaches its usual status, such as `active` or `available`. When the order is declined, canceled or expires, or creation fails, the resource ends `failed` and `failure_reason` states why; the charge for a resource that failed after acceptance is refunded. Read the order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid options Billing offers for them, in the currency of the project's current billing account, or null when the project has no billing account. They are list amounts before promotion codes, not a checkout guarantee. A purchase chooses one option with `billing`, which applies to all of its components. Every purchase and change has a quote operation beside it, at the same path followed by `/quote`, which returns what checkout would collect without ordering anything.
+ * - **Checkout.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; insufficient funds refuse the request with HTTP 422 `BILLING_INSUFFICIENT_FUNDS`, and nothing is created. With `checkout.mode` set to `deferred`, the resources are returned `pending` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **Operations.** Requests such as starting, stopping, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `operation` field names it; the field is null once the operation has finished, and the resource then shows the result. A resource with an operation in progress refuses another operation with HTTP 409 `COMPUTE_RESOURCE_BUSY`; an operation involving two resources, such as attaching a disk, is refused when either has one. A purchased change, such as a resize, is an operation from the moment its order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records its `order_id`, `order_item_id` and `subscription_id`. The subscription is `pending` until the order is accepted, `provisioning` while the resource is created, and `active` once it is delivered. Bandwidth is a property of its floating IP, not a separate resource. Snapshots use a purchased per-region count quota, and backups are metered on the region's backup service; neither has an order or subscription of its own.
+ * - **Availability zones.** A disk and an instance must reside in the same availability zone to be attached. Instance types and disk types are each bound to one availability zone, so choosing a type determines the zone.
+ * - **IPv6 is not sold separately.** Once enabled on a private network, IPv6 addresses are assigned to the instances in that network automatically; they can be neither requested nor released individually.
+ * - **Floating IPs have a cooldown period.** A released address is neither available for re-allocation nor handed to another user for some time, so that DNS records and allow-lists still pointing at it do not break immediately.
+ * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { Money } from "./money.zod.js";
+import { OrderItemStatus } from "./orderItemStatus.zod.js";
+import { Product } from "./product.zod.js";
+import { ProductID } from "./productID.zod.js";
+import { RefundPolicy } from "./refundPolicy.zod.js";
+import { TerminationPolicyBfdab9f } from "./terminationPolicyBfdab9f.zod.js";
+export const orderItemPositionMin = 0;
+export const OrderItem = zod
+    .strictObject({
+    invoice_item_ids: zod
+        .array(zod.uuid())
+        .optional()
+        .describe("Financial lines produced by this purchase item, including setup charges."),
+    position: zod.int().min(orderItemPositionMin).optional(),
+    configuration: zod.record(zod.string(), zod.unknown()).optional(),
+    subscription_id: zod
+        .uuid()
+        .optional()
+        .describe("Stable Billing subscription ID. A new prepaid or postpaid service purchase returns the\npending subscription here; renewals and changes reference the existing subscription, which\nkeeps its ID. Absent for delivery without a subscription. This is not a business resource ID."),
+    interval: zod.enum(["none", "day", "month", "year"]),
+    interval_count: zod.int().min(1).optional(),
+    termination_policy: TerminationPolicyBfdab9f.optional(),
+    refund_policy: RefundPolicy.optional(),
+    refund_monthly_amount: zod
+        .string()
+        .nullish()
+        .describe("Prepaid items only: the plan's one-month prepaid price for this item's quantity before tax, frozen\nat purchase, used to value time used under a prorated refund or a downgrade. Null when the plan has\nno prepaid period shorter than the one bought."),
+    refund_hourly_amount: zod
+        .string()
+        .nullish()
+        .describe("Prepaid items only: the plan's postpaid hourly price for this item's quantity before tax, frozen at\npurchase, used for time used short of a full month. Null when the plan has no postpaid price."),
+    recurring_amount: zod.string().optional(),
+    setup_amount: zod.string().optional(),
+    charge_type: zod
+        .enum(["postpaid", "prepaid", "one_time"])
+        .describe("The payment timing of the selected price."),
+    tax_amount: zod
+        .string()
+        .optional()
+        .describe("Total tax after discounts, including any tax already included in the price."),
+    tax_included_amount: zod
+        .string()
+        .optional()
+        .describe("The part of tax_amount already included in gross_amount; it is not charged again."),
+    id: zod.uuid(),
+    order_id: zod.uuid().optional(),
+    price_id: zod.uuid(),
+    product_id: ProductID.optional(),
+    product: Product.optional(),
+    plan_id: zod.uuid().describe("Which plan was bought."),
+    plan_name: zod
+        .string()
+        .describe("What it was called when bought. It does not follow later catalogue renames and is\nnot translated."),
+    quantity: zod.string(),
+    unit_amount: Money.optional().describe("The unit amount of the price this line is charged under. Absent for a tiered price, which has no\nsingle unit amount, and for a change that takes effect at once, which is charged as `gross_amount`\ndescribes."),
+    gross_amount: Money.optional().describe("Before discounts: the price applied to the quantity, which for a per-unit price is `unit_amount`\ntimes `quantity`; a minimum charge can make it higher. For an upgrade that takes effect at once it is\nthe new price minus the old price for the time left in the paid period, both at the subscription's\nown period price, and the period end does not move; a downgrade charges nothing and may refund the\ndifference instead. A change between equal period prices charges and refunds nothing. The setup fee is not part of it; see `setup_amount`.\n\nUnder an inclusive tax rate it includes tax, as the price does, and the included part is\n`tax_included_amount`. A renewal at the agreed terms is the exception: the agreed amount excludes\ntax, and tax is added to it."),
+    discount_amount: Money.optional().describe("The reduction on this line: from the coupon the order uses and, for a renewal at the agreed terms,\nfrom the discount the subscription carries.\n\nA carried discount is part of the agreed amount. It is listed here, and `gross_amount` is then\n`unit_amount` times `quantity`, except in two cases where `gross_amount` is the agreed amount and\nthe carried discount is already reflected in it: the renewal order also uses a coupon the account\nholds, or the account's tax rate is inclusive."),
+    amount: Money.optional().describe("`gross_amount` less `discount_amount`."),
+    currency: zod.string(),
+    period_start: zod.iso.datetime({ offset: true }).nullish(),
+    period_end: zod.iso.datetime({ offset: true }).nullish(),
+    status: OrderItemStatus,
+})
+    .describe("Frozen purchase terms. Monetary fields come from related invoice-line snapshots and are zero\nfor a line with no immediate charge, such as postpaid admission. Later catalog changes do not reprice this line. A new service\npurchase creates its pending subscription when this item is recorded, not when payment succeeds.");