@leaflow/sdk 0.0.0-dev.31.ge5a1cab → 0.0.0-dev.313.gcc57e2c

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

@@ -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 declare const Quote: zod.ZodObject<{
+    items: zod.ZodArray<zod.ZodObject<{
+        plan_name: zod.ZodString;
+        unit_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
+        quantity: zod.ZodString;
+        amount: zod.ZodString;
+        discount_amount: zod.ZodString;
+        tax_amount: zod.ZodString;
+        tax_included_amount: zod.ZodString;
+        total: zod.ZodString;
+        estimated_usage_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
+        currency: zod.ZodString;
+    }, zod.z.core.$strict>>;
+    subtotal: zod.ZodString;
+    discount_amount: zod.ZodString;
+    tax_amount: zod.ZodString;
+    total: zod.ZodString;
+    estimated_usage_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
+    currency: zod.ZodString;
+    proration_date: zod.ZodNullable<zod.z.ZodISODateTime>;
+    refundable_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
+}, zod.z.core.$strict>;
+export type Quote = zod.input<typeof Quote>;
+export type QuoteOutput = zod.output<typeof Quote>;

package/dist/compute/v1/generated/validators/quote.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";
+import { Money } from "./money.zod.js";
+import { QuoteItemDc1fddb } from "./quoteItemDc1fddb.zod.js";
+export const Quote = zod
+    .strictObject({
+    items: zod
+        .array(QuoteItemDc1fddb)
+        .describe("One line for each item the purchase would order, in the order it would order them."),
+    subtotal: Money.describe("Sum of line amounts before discounts, less tax already included in the discounted line\namounts, as on an invoice."),
+    discount_amount: Money.describe("Sum of line discounts."),
+    tax_amount: Money.describe("Sum of tax on the discounted line amounts."),
+    total: Money.describe("subtotal minus discount_amount plus tax_amount: what checkout collects, before applying\ncredit grants or balance. Equals the sum of line totals and excludes estimated_usage_amount."),
+    estimated_usage_amount: zod
+        .union([Money, zod.null()])
+        .describe("Sum of the lines' estimated_usage_amount. A projection, not part of total and not collected at\ncheckout. Null when no usage estimate is requested."),
+    currency: zod.string(),
+    proration_date: zod.iso
+        .datetime({ offset: true })
+        .nullable()
+        .describe("Changes only; null otherwise. The instant the change is priced from. Pass it with the change so the\norder is priced from the same instant."),
+    refundable_amount: zod
+        .union([Money, zod.null()])
+        .describe("Changes that lower the price only; null otherwise. What the change would return to the original\npayment sources, including the tax paid on it. total is zero for such a change."),
+})
+    .describe("A price preview for the purchase described by a service, calculated by Billing. Nothing is saved,\ncharged or reserved, and no discount redemption is consumed. Account discounts and tax are\nevaluated as for automatic checkout. Promotion codes are evaluated through Billing quote operations.\nAll amounts use currency. This preview does not lock prices or guarantee discount availability.\nSuccess includes complete checkout amounts and every requested usage estimate. If any item or\nrequested usage estimate cannot be calculated, the operation returns its existing structured\nerror response; it never returns a partial quote with HTTP 200.");

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

@@ -0,0 +1,115 @@
+/**
+ * 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 Quote5f60d00: zod.ZodObject<{
+    subtotal: zod.ZodString;
+    discount_amount: zod.ZodString;
+    tax_amount: zod.ZodString;
+    discount: zod.ZodUnion<readonly [zod.ZodObject<{
+        type: zod.ZodEnum<{
+            promotion_code: "promotion_code";
+            account_discount: "account_discount";
+        }>;
+        name: zod.ZodString;
+        promotion_code: zod.ZodNullable<zod.ZodString>;
+    }, zod.z.core.$strict>, zod.ZodNull]>;
+    items: zod.ZodArray<zod.ZodObject<{
+        tax_amount: zod.ZodString;
+        tax_included_amount: zod.ZodString;
+        index: zod.ZodInt;
+        order_item_id: zod.ZodOptional<zod.ZodUUID>;
+        price_id: zod.ZodUUID;
+        plan_name: zod.ZodString;
+        unit_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
+        quantity: zod.ZodString;
+        amount: zod.ZodString;
+        discount_amount: zod.ZodString;
+        total: zod.ZodString;
+        currency: zod.ZodString;
+    }, zod.z.core.$strict>>;
+    renewals: zod.ZodArray<zod.ZodObject<{
+        index: zod.ZodInt;
+        subscription_id: zod.ZodUUID;
+        price_id: zod.ZodUUID;
+        interval: zod.ZodEnum<{
+            day: "day";
+            month: "month";
+            year: "year";
+        }>;
+        interval_count: zod.ZodInt;
+        periods: zod.ZodInt;
+        amount: zod.ZodString;
+        discount_amount: zod.ZodString;
+        tax_amount: zod.ZodString;
+        tax_included_amount: zod.ZodString;
+        total: zod.ZodString;
+    }, zod.z.core.$strict>>;
+    cancellation: zod.ZodOptional<zod.ZodObject<{
+        mode: zod.ZodEnum<{
+            immediate: "immediate";
+            period_end: "period_end";
+        }>;
+        scheduled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+        proration_date: zod.ZodOptional<zod.z.ZodISODateTime>;
+        currency: zod.ZodString;
+        unused_amount: zod.ZodString;
+        refundable_amount: zod.ZodString;
+        refund_amount: zod.ZodString;
+        credit_amount: zod.ZodString;
+        tax_amount: zod.ZodString;
+        forfeited_amount: zod.ZodString;
+        items: zod.ZodArray<zod.ZodObject<{
+            subscription_id: zod.ZodUUID;
+            plan_id: zod.ZodUUID;
+            plan_name: zod.ZodString;
+            project: zod.ZodOptional<zod.ZodUnion<readonly [zod.ZodObject<{
+                id: zod.ZodUUID;
+                name: zod.ZodString;
+            }, zod.z.core.$strict>, zod.ZodNull]>>;
+            charge_type: zod.ZodEnum<{
+                postpaid: "postpaid";
+                prepaid: "prepaid";
+                one_time: "one_time";
+            }>;
+            auto_renew: zod.ZodBoolean;
+            unused_amount: zod.ZodString;
+            refundable_amount: zod.ZodString;
+            refund_amount: zod.ZodString;
+            credit_amount: zod.ZodString;
+            tax_amount: zod.ZodString;
+            forfeited_amount: zod.ZodString;
+        }, zod.z.core.$strict>>;
+    }, zod.z.core.$strict>>;
+    total: zod.ZodString;
+    currency: zod.ZodString;
+    refund: zod.ZodOptional<zod.ZodObject<{
+        order_id: zod.ZodUUID;
+        refundable_amount: zod.ZodString;
+        refund_amount: zod.ZodString;
+        credit_amount: zod.ZodString;
+        currency: zod.ZodString;
+    }, zod.z.core.$strict>>;
+}, zod.z.core.$strict>;
+export type Quote5f60d00 = zod.input<typeof Quote5f60d00>;
+export type Quote5f60d00Output = zod.output<typeof Quote5f60d00>;

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

@@ -0,0 +1,46 @@
+/**
+ * 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 { CancellationRefundPreview } from "./cancellationRefundPreview.zod.js";
+import { Money } from "./money.zod.js";
+import { OrderRefundQuote } from "./orderRefundQuote.zod.js";
+import { QuotedDiscount } from "./quotedDiscount.zod.js";
+import { QuoteItem } from "./quoteItem.zod.js";
+import { QuoteRenewalResult } from "./quoteRenewalResult.zod.js";
+export const Quote5f60d00 = zod
+    .strictObject({
+    subtotal: Money,
+    discount_amount: Money,
+    tax_amount: Money,
+    discount: zod
+        .union([QuotedDiscount, zod.null()])
+        .describe("The discount evaluated for a purchase or order, without applying it. Null when none is selected or\nwhen quoting renewals or a cancellation. A confirmed order reports its recorded discount."),
+    items: zod.array(QuoteItem),
+    renewals: zod.array(QuoteRenewalResult),
+    cancellation: CancellationRefundPreview.optional().describe("What the cancellation requested would return. Present only when one was requested."),
+    total: Money,
+    currency: zod.string(),
+    refund: OrderRefundQuote.optional().describe("Present only when an order refund was requested. Nothing is collectible for this target."),
+})
+    .describe("A complete calculation in one billing-account currency, without saving a quote or reserving funds or\nredemptions. The request fails if any item cannot be priced. Requested future usage estimates are\nincluded in totals for reporting and are not collectible at checkout. Only an existing-order quote\nprovides that order's checkout amount.");

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

@@ -0,0 +1,115 @@
+/**
+ * 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 QuoteA200529: zod.ZodObject<{
+    subtotal: zod.ZodString;
+    discount_amount: zod.ZodString;
+    tax_amount: zod.ZodString;
+    discount: zod.ZodUnion<readonly [zod.ZodObject<{
+        type: zod.ZodEnum<{
+            promotion_code: "promotion_code";
+            account_discount: "account_discount";
+        }>;
+        name: zod.ZodString;
+        promotion_code: zod.ZodNullable<zod.ZodString>;
+    }, zod.z.core.$strict>, zod.ZodNull]>;
+    items: zod.ZodArray<zod.ZodObject<{
+        tax_amount: zod.ZodString;
+        tax_included_amount: zod.ZodString;
+        index: zod.ZodInt;
+        order_item_id: zod.ZodOptional<zod.ZodUUID>;
+        price_id: zod.ZodUUID;
+        plan_name: zod.ZodString;
+        unit_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
+        quantity: zod.ZodString;
+        amount: zod.ZodString;
+        discount_amount: zod.ZodString;
+        total: zod.ZodString;
+        currency: zod.ZodString;
+    }, zod.z.core.$strict>>;
+    renewals: zod.ZodArray<zod.ZodObject<{
+        index: zod.ZodInt;
+        subscription_id: zod.ZodUUID;
+        price_id: zod.ZodUUID;
+        interval: zod.ZodEnum<{
+            day: "day";
+            month: "month";
+            year: "year";
+        }>;
+        interval_count: zod.ZodInt;
+        periods: zod.ZodInt;
+        amount: zod.ZodString;
+        discount_amount: zod.ZodString;
+        tax_amount: zod.ZodString;
+        tax_included_amount: zod.ZodString;
+        total: zod.ZodString;
+    }, zod.z.core.$strict>>;
+    cancellation: zod.ZodOptional<zod.ZodObject<{
+        mode: zod.ZodEnum<{
+            immediate: "immediate";
+            period_end: "period_end";
+        }>;
+        scheduled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+        proration_date: zod.ZodOptional<zod.z.ZodISODateTime>;
+        currency: zod.ZodString;
+        unused_amount: zod.ZodString;
+        refundable_amount: zod.ZodString;
+        refund_amount: zod.ZodString;
+        credit_amount: zod.ZodString;
+        tax_amount: zod.ZodString;
+        forfeited_amount: zod.ZodString;
+        items: zod.ZodArray<zod.ZodObject<{
+            subscription_id: zod.ZodUUID;
+            plan_id: zod.ZodUUID;
+            plan_name: zod.ZodString;
+            project: zod.ZodOptional<zod.ZodUnion<readonly [zod.ZodObject<{
+                id: zod.ZodUUID;
+                name: zod.ZodString;
+            }, zod.z.core.$strict>, zod.ZodNull]>>;
+            charge_type: zod.ZodEnum<{
+                postpaid: "postpaid";
+                prepaid: "prepaid";
+                one_time: "one_time";
+            }>;
+            auto_renew: zod.ZodBoolean;
+            unused_amount: zod.ZodString;
+            refundable_amount: zod.ZodString;
+            refund_amount: zod.ZodString;
+            credit_amount: zod.ZodString;
+            tax_amount: zod.ZodString;
+            forfeited_amount: zod.ZodString;
+        }, zod.z.core.$strict>>;
+    }, zod.z.core.$strict>>;
+    total: zod.ZodString;
+    currency: zod.ZodString;
+    refund: zod.ZodOptional<zod.ZodObject<{
+        order_id: zod.ZodUUID;
+        refundable_amount: zod.ZodString;
+        refund_amount: zod.ZodString;
+        credit_amount: zod.ZodString;
+        currency: zod.ZodString;
+    }, zod.z.core.$strict>>;
+}, zod.z.core.$strict>;
+export type QuoteA200529 = zod.input<typeof QuoteA200529>;
+export type QuoteA200529Output = zod.output<typeof QuoteA200529>;

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

@@ -0,0 +1,26 @@
+/**
+ * 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 { Quote5f60d00 } from "./quote5f60d00.zod.js";
+export const QuoteA200529 = Quote5f60d00;

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

@@ -0,0 +1,34 @@
+/**
+ * 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 quoteCancellationSubscriptionIdsMax = 50;
+export declare const QuoteCancellation: zod.ZodObject<{
+    subscription_ids: zod.ZodArray<zod.ZodUUID>;
+    mode: zod.ZodEnum<{
+        immediate: "immediate";
+        period_end: "period_end";
+    }>;
+}, zod.z.core.$strict>;
+export type QuoteCancellation = zod.input<typeof QuoteCancellation>;
+export type QuoteCancellationOutput = zod.output<typeof QuoteCancellation>;

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

@@ -0,0 +1,36 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Compute API
+ * Leaflow Compute user API for managing instances, disks, snapshots, backups, images, private networks, subnets, routes, security groups, network interfaces and floating IPs.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `scopedTokenAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **Purchases.** A purchase that creates resources returns them together with a PlacedOrder. They are readable at once and start as `pending`: the order has not been accepted, nothing exists in the cloud, no inventory such as an address is held, and fields known only after allocation, such as addresses, are null. Once Billing accepts the order, a resource becomes `provisioning` and then reaches its usual status, such as `active` or `available`. When the order is declined, canceled or expires, or creation fails, the resource ends `failed` and `failure_reason` states why; the charge for a resource that failed after acceptance is refunded. Read the order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid options Billing offers for them, in the currency of the project's current billing account, or null when the project has no billing account. They are list amounts before promotion codes, not a checkout guarantee. A purchase chooses one option with `billing`, which applies to all of its components. Every purchase and change has a quote operation beside it, at the same path followed by `/quote`, which returns what checkout would collect without ordering anything.
+ * - **Checkout.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; insufficient funds refuse the request with HTTP 422 `BILLING_INSUFFICIENT_FUNDS`, and nothing is created. With `checkout.mode` set to `deferred`, the resources are returned `pending` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **Operations.** Requests such as starting, stopping, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `operation` field names it; the field is null once the operation has finished, and the resource then shows the result. A resource with an operation in progress refuses another operation with HTTP 409 `COMPUTE_RESOURCE_BUSY`; an operation involving two resources, such as attaching a disk, is refused when either has one. A purchased change, such as a resize, is an operation from the moment its order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records its `order_id`, `order_item_id` and `subscription_id`. The subscription is `pending` until the order is accepted, `provisioning` while the resource is created, and `active` once it is delivered. Bandwidth is a property of its floating IP, not a separate resource. Snapshots use a purchased per-region count quota, and backups are metered on the region's backup service; neither has an order or subscription of its own.
+ * - **Availability zones.** A disk and an instance must reside in the same availability zone to be attached. Instance types and disk types are each bound to one availability zone, so choosing a type determines the zone.
+ * - **IPv6 is not sold separately.** Once enabled on a private network, IPv6 addresses are assigned to the instances in that network automatically; they can be neither requested nor released individually.
+ * - **Floating IPs have a cooldown period.** A released address is neither available for re-allocation nor handed to another user for some time, so that DNS records and allow-lists still pointing at it do not break immediately.
+ * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { TerminationPolicyBfdab9f } from "./terminationPolicyBfdab9f.zod.js";
+export const quoteCancellationSubscriptionIdsMax = 50;
+export const QuoteCancellation = zod
+    .strictObject({
+    subscription_ids: zod
+        .array(zod.uuid())
+        .min(1)
+        .max(quoteCancellationSubscriptionIdsMax)
+        .describe("The subscriptions to end together, all of one service. Every subscription released with a resource must be included."),
+    mode: TerminationPolicyBfdab9f,
+})
+    .describe("A cancellation to quote: what ending these subscriptions together would return. One mode per\nrequest; to compare, quote `immediate` and `period_end` separately.\n\nRefused with 409 `BILLING_SUBSCRIPTION_OPERATION_PENDING` when a subscription is already being\ncanceled (`meta.cancellation_id`), is being reclaimed (`meta.reason` `reclaim_requested`) or has a\npaid change still waiting to switch (`meta.order_id`).");

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

@@ -0,0 +1,41 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Compute API
+ * Leaflow Compute user API for managing instances, disks, snapshots, backups, images, private networks, subnets, routes, security groups, network interfaces and floating IPs.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `scopedTokenAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **Purchases.** A purchase that creates resources returns them together with a PlacedOrder. They are readable at once and start as `pending`: the order has not been accepted, nothing exists in the cloud, no inventory such as an address is held, and fields known only after allocation, such as addresses, are null. Once Billing accepts the order, a resource becomes `provisioning` and then reaches its usual status, such as `active` or `available`. When the order is declined, canceled or expires, or creation fails, the resource ends `failed` and `failure_reason` states why; the charge for a resource that failed after acceptance is refunded. Read the order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid options Billing offers for them, in the currency of the project's current billing account, or null when the project has no billing account. They are list amounts before promotion codes, not a checkout guarantee. A purchase chooses one option with `billing`, which applies to all of its components. Every purchase and change has a quote operation beside it, at the same path followed by `/quote`, which returns what checkout would collect without ordering anything.
+ * - **Checkout.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; insufficient funds refuse the request with HTTP 422 `BILLING_INSUFFICIENT_FUNDS`, and nothing is created. With `checkout.mode` set to `deferred`, the resources are returned `pending` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **Operations.** Requests such as starting, stopping, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `operation` field names it; the field is null once the operation has finished, and the resource then shows the result. A resource with an operation in progress refuses another operation with HTTP 409 `COMPUTE_RESOURCE_BUSY`; an operation involving two resources, such as attaching a disk, is refused when either has one. A purchased change, such as a resize, is an operation from the moment its order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records its `order_id`, `order_item_id` and `subscription_id`. The subscription is `pending` until the order is accepted, `provisioning` while the resource is created, and `active` once it is delivered. Bandwidth is a property of its floating IP, not a separate resource. Snapshots use a purchased per-region count quota, and backups are metered on the region's backup service; neither has an order or subscription of its own.
+ * - **Availability zones.** A disk and an instance must reside in the same availability zone to be attached. Instance types and disk types are each bound to one availability zone, so choosing a type determines the zone.
+ * - **IPv6 is not sold separately.** Once enabled on a private network, IPv6 addresses are assigned to the instances in that network automatically; they can be neither requested nor released individually.
+ * - **Floating IPs have a cooldown period.** A released address is neither available for re-allocation nor handed to another user for some time, so that DNS records and allow-lists still pointing at it do not break immediately.
+ * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const quoteItemIndexMin = 0;
+export declare const QuoteItem: zod.ZodObject<{
+    tax_amount: zod.ZodString;
+    tax_included_amount: zod.ZodString;
+    index: zod.ZodInt;
+    order_item_id: zod.ZodOptional<zod.ZodUUID>;
+    price_id: zod.ZodUUID;
+    plan_name: zod.ZodString;
+    unit_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
+    quantity: zod.ZodString;
+    amount: zod.ZodString;
+    discount_amount: zod.ZodString;
+    total: zod.ZodString;
+    currency: zod.ZodString;
+}, zod.z.core.$strict>;
+export type QuoteItem = zod.input<typeof QuoteItem>;
+export type QuoteItemOutput = zod.output<typeof QuoteItem>;

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

@@ -0,0 +1,54 @@
+/**
+ * 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";
+export const quoteItemIndexMin = 0;
+export const QuoteItem = zod
+    .strictObject({
+    tax_amount: Money,
+    tax_included_amount: Money,
+    index: zod
+        .int()
+        .min(quoteItemIndexMin)
+        .describe("Zero-based request line index, or the recorded order item's position for an order quote."),
+    order_item_id: zod
+        .uuid()
+        .optional()
+        .describe("Present for an existing order quote; identifies the recorded item being priced."),
+    price_id: zod
+        .uuid()
+        .describe("The selected price, including when the request identified it indirectly."),
+    plan_name: zod.string(),
+    unit_amount: zod
+        .union([Money, zod.null()])
+        .describe("Unit price before discounts. Null when no single unit price applies, such as tiered or multiple-rate pricing."),
+    quantity: zod
+        .string()
+        .describe("The quantity priced. When duration_seconds is supplied for metered usage, this is quantity multiplied by that duration."),
+    amount: Money.describe("Amount before discounts and including any setup charge. For requested future usage this is an estimate, not a collectible checkout amount."),
+    discount_amount: Money,
+    total: Money,
+    currency: zod.string(),
+})
+    .describe("One fully calculated purchase, estimated postpaid usage or recorded order item. Amounts use the\nbilling-account currency. An item with no immediate charge has zero checkout amounts.");