@leaflow/sdk 0.131.0 → 0.133.0

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

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

@@ -1,94 +0,0 @@
-/**
- * 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()
-        .describe("The start of the service period this line paid for. Frozen at placement for renewals and period-end changes; for a prepaid line of a new purchase, fixed from the second its invoice is paid and kept when delivery is confirmed. Absent for postpaid and one-time lines."),
-    period_end: zod.iso
-        .datetime({ offset: true })
-        .nullish()
-        .describe("The end of that service period, exclusive."),
-    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.");

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

@@ -1,90 +0,0 @@
-/**
- * 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 OrderItemList: zod.ZodObject<{
-    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>>;
-    pagination: zod.ZodObject<{
-        page: zod.ZodInt;
-        page_size: zod.ZodInt;
-        total_count: zod.ZodOptional<zod.ZodInt>;
-    }, zod.z.core.$strict>;
-}, zod.z.core.$strict>;
-export type OrderItemList = zod.input<typeof OrderItemList>;
-export type OrderItemListOutput = zod.output<typeof OrderItemList>;

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

@@ -1,30 +0,0 @@
-/**
- * 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 { OffsetPagination } from "./offsetPagination.zod.js";
-import { OrderItem } from "./orderItem.zod.js";
-export const OrderItemList = zod.strictObject({
-    items: zod.array(OrderItem),
-    pagination: OffsetPagination,
-});

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

@@ -1,32 +0,0 @@
-/**
- * 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 OrderItemStatus: zod.ZodEnum<{
-    pending: "pending";
-    completed: "completed";
-    failed: "failed";
-    canceled: "canceled";
-}>;
-export type OrderItemStatus = zod.input<typeof OrderItemStatus>;
-export type OrderItemStatusOutput = zod.output<typeof OrderItemStatus>;

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

@@ -1,27 +0,0 @@
-/**
- * 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 OrderItemStatus = zod
-    .enum(["pending", "completed", "failed", "canceled"])
-    .describe("`pending` is waiting to be set up. `completed` was confirmed by the service.\n`failed` was not set up and its amount was refunded to the original payment sources.\n`canceled` was confirmed withdrawn without delivery; any collected amount is returned. A completed item is ended by canceling\nits subscription.");

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

@@ -1,165 +0,0 @@
-/**
- * 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 OrderList: zod.ZodObject<{
-    items: zod.ZodArray<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>>;
-    pagination: zod.ZodObject<{
-        page: zod.ZodInt;
-        page_size: zod.ZodInt;
-        total_count: zod.ZodOptional<zod.ZodInt>;
-    }, zod.z.core.$strict>;
-}, zod.z.core.$strict>;
-export type OrderList = zod.input<typeof OrderList>;
-export type OrderListOutput = zod.output<typeof OrderList>;

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

@@ -1,30 +0,0 @@
-/**
- * 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 { OffsetPagination } from "./offsetPagination.zod.js";
-import { Order } from "./order.zod.js";
-export const OrderList = zod.strictObject({
-    items: zod.array(Order),
-    pagination: OffsetPagination,
-});

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

@@ -1,33 +0,0 @@
-/**
- * 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 OrderRefundQuote: 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>;
-export type OrderRefundQuote = zod.input<typeof OrderRefundQuote>;
-export type OrderRefundQuoteOutput = zod.output<typeof OrderRefundQuote>;