@leaflow/sdk 0.121.0 → 0.123.0

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

@@ -0,0 +1,51 @@
+/**
+ * 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 StatementSummary: zod.ZodObject<{
+    statement_id: zod.ZodUUID;
+    currency: zod.ZodString;
+    estimated: zod.ZodBoolean;
+    calculated_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+    group_by: zod.ZodEnum<{
+        project: "project";
+        product: "product";
+        meter: "meter";
+    }>;
+    items: zod.ZodArray<zod.ZodObject<{
+        project_id: zod.ZodOptional<zod.ZodUUID>;
+        product_id: zod.ZodOptional<zod.ZodString>;
+        meter_id: zod.ZodOptional<zod.ZodUUID>;
+        unit: zod.ZodOptional<zod.ZodString>;
+        quantity: zod.ZodOptional<zod.ZodString>;
+        deducted_quantity: zod.ZodOptional<zod.ZodString>;
+        amount: zod.ZodString;
+    }, 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 StatementSummary = zod.input<typeof StatementSummary>;
+export type StatementSummaryOutput = zod.output<typeof StatementSummary>;

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

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

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

@@ -0,0 +1,127 @@
+/**
+ * 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 subscriptionDiscountedRenewalsRemainingMin = 0;
+export declare const Subscription: zod.ZodObject<{
+    currency: zod.ZodString;
+    charge_type: zod.ZodEnum<{
+        postpaid: "postpaid";
+        prepaid: "prepaid";
+        one_time: "one_time";
+    }>;
+    interval: zod.ZodEnum<{
+        none: "none";
+        day: "day";
+        month: "month";
+        year: "year";
+    }>;
+    interval_count: zod.ZodOptional<zod.ZodInt>;
+    recurring_amount: zod.ZodOptional<zod.ZodString>;
+    termination_policy: zod.ZodOptional<zod.ZodEnum<{
+        immediate: "immediate";
+        period_end: "period_end";
+    }>>;
+    refund_policy: zod.ZodOptional<zod.ZodEnum<{
+        none: "none";
+        prorated: "prorated";
+    }>>;
+    order_item_id: zod.ZodOptional<zod.ZodUUID>;
+    replaces_subscription_id: zod.ZodOptional<zod.ZodUUID>;
+    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>>;
+    discounted_renewals_remaining: zod.ZodOptional<zod.ZodInt>;
+    suspend_reason: zod.ZodOptional<zod.ZodString>;
+    billing_cycle_anchor: zod.ZodOptional<zod.z.ZodISODateTime>;
+    cancellation: zod.ZodOptional<zod.ZodObject<{
+        reason: zod.ZodOptional<zod.ZodString>;
+        cancellation_id: zod.ZodOptional<zod.ZodUUID>;
+        id: zod.ZodUUID;
+        subscription_id: zod.ZodUUID;
+        status: zod.ZodEnum<{
+            completed: "completed";
+            failed: "failed";
+            requested: "requested";
+            scheduled: "scheduled";
+            releasing: "releasing";
+            canceled: "canceled";
+        }>;
+        mode: zod.ZodEnum<{
+            immediate: "immediate";
+            period_end: "period_end";
+        }>;
+        requested_at: zod.z.ZodISODateTime;
+        scheduled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+        effective_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+        completed_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+        release_started_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+        canceled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+        forfeit_remaining_value: zod.ZodBoolean;
+        failure_code: zod.ZodOptional<zod.ZodString>;
+        failure_reason: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>>;
+    default_payment_method_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
+    created_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+    id: zod.ZodUUID;
+    billing_account_id: zod.ZodInt;
+    account: zod.ZodObject<{
+        id: zod.ZodInt;
+        name: zod.ZodString;
+        currency: zod.ZodString;
+    }, zod.z.core.$strict>;
+    product_id: zod.ZodString;
+    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]>>;
+    product: 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;
+    price_id: zod.ZodUUID;
+    quantity: zod.ZodString;
+    current_term_end: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+    current_period_start: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+    current_period_end: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+    auto_renew: zod.ZodBoolean;
+    status: zod.ZodEnum<{
+        pending: "pending";
+        active: "active";
+        suspended: "suspended";
+        canceled: "canceled";
+        provisioning: "provisioning";
+        terminated: "terminated";
+    }>;
+    started_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+    ended_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+}, zod.z.core.$strict>;
+export type Subscription = zod.input<typeof Subscription>;
+export type SubscriptionOutput = zod.output<typeof Subscription>;

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

@@ -0,0 +1,108 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Compute API
+ * Leaflow Compute user API for managing instances, disks, snapshots, backups, images, private networks, subnets, routes, security groups, network interfaces and floating IPs.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `scopedTokenAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **Purchases.** A purchase that creates resources returns them together with a PlacedOrder. They are readable at once and start as `pending`: the order has not been accepted, nothing exists in the cloud, no inventory such as an address is held, and fields known only after allocation, such as addresses, are null. Once Billing accepts the order, a resource becomes `provisioning` and then reaches its usual status, such as `active` or `available`. When the order is declined, canceled or expires, or creation fails, the resource ends `failed` and `failure_reason` states why; the charge for a resource that failed after acceptance is refunded. Read the order in Billing for checkout and payment progress.
+ * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid options Billing offers for them, in the currency of the project's current billing account, or null when the project has no billing account. They are list amounts before promotion codes, not a checkout guarantee. A purchase chooses one option with `billing`, which applies to all of its components. Every purchase and change has a quote operation beside it, at the same path followed by `/quote`, which returns what checkout would collect without ordering anything.
+ * - **Checkout.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; insufficient funds refuse the request with HTTP 422 `BILLING_INSUFFICIENT_FUNDS`, and nothing is created. With `checkout.mode` set to `deferred`, the resources are returned `pending` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
+ * - **Operations.** Requests such as starting, stopping, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `operation` field names it; the field is null once the operation has finished, and the resource then shows the result. A resource with an operation in progress refuses another operation with HTTP 409 `COMPUTE_RESOURCE_BUSY`; an operation involving two resources, such as attaching a disk, is refused when either has one. A purchased change, such as a resize, is an operation from the moment its order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
+ * - **Billing relationships.** A purchased resource records its `order_id`, `order_item_id` and `subscription_id`. The subscription is `pending` until the order is accepted, `provisioning` while the resource is created, and `active` once it is delivered. Bandwidth is a property of its floating IP, not a separate resource. Snapshots use a purchased per-region count quota, and backups are metered on the region's backup service; neither has an order or subscription of its own.
+ * - **Availability zones.** A disk and an instance must reside in the same availability zone to be attached. Instance types and disk types are each bound to one availability zone, so choosing a type determines the zone.
+ * - **IPv6 is not sold separately.** Once enabled on a private network, IPv6 addresses are assigned to the instances in that network automatically; they can be neither requested nor released individually.
+ * - **Floating IPs have a cooldown period.** A released address is neither available for re-allocation nor handed to another user for some time, so that DNS records and allow-lists still pointing at it do not break immediately.
+ * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { AccountIdentity } from "./accountIdentity.zod.js";
+import { NamedIdentity } from "./namedIdentity.zod.js";
+import { ObjectIdentity } from "./objectIdentity.zod.js";
+import { Product } from "./product.zod.js";
+import { ProductID } from "./productID.zod.js";
+import { RefundPolicy } from "./refundPolicy.zod.js";
+import { SubscriptionCancellation } from "./subscriptionCancellation.zod.js";
+import { TerminationPolicyBfdab9f } from "./terminationPolicyBfdab9f.zod.js";
+export const subscriptionDiscountedRenewalsRemainingMin = 0;
+export const Subscription = zod
+    .strictObject({
+    currency: zod.string(),
+    charge_type: zod.enum(["postpaid", "prepaid", "one_time"]),
+    interval: zod.enum(["none", "day", "month", "year"]),
+    interval_count: zod.int().min(1).optional(),
+    recurring_amount: zod
+        .string()
+        .optional()
+        .describe("Whole-subscription prepaid renewal amount, after continuing discounts and before tax.\nPending subscriptions show base terms until paying the order fixes any new continuing discount.\nAbsent for other charge types."),
+    termination_policy: TerminationPolicyBfdab9f.optional(),
+    refund_policy: RefundPolicy.optional(),
+    order_item_id: zod.uuid().optional(),
+    replaces_subscription_id: zod
+        .uuid()
+        .optional()
+        .describe("Present only on subscriptions created by an earlier change that replaced the subscription. A change now keeps the subscription ID."),
+    coupon_id: zod.uuid().optional(),
+    coupon: ObjectIdentity.optional(),
+    discounted_renewals_remaining: zod
+        .int()
+        .min(subscriptionDiscountedRenewalsRemainingMin)
+        .optional(),
+    suspend_reason: zod.string().optional(),
+    billing_cycle_anchor: zod.iso.datetime({ offset: true }).optional(),
+    cancellation: SubscriptionCancellation.optional(),
+    default_payment_method_id: zod
+        .uuid()
+        .nullish()
+        .describe("The saved payment method automatic renewal charges after the account's balance and credits,\nbefore the account's default payment method. Set when the purchase, a renewal or a change is paid with a\nsaved payment method; paying any other way leaves it unchanged. It is used only while it belongs to the\naccount that pays the renewal."),
+    created_at: zod.iso.datetime({ offset: true }).optional(),
+    id: zod.uuid(),
+    billing_account_id: zod
+        .int()
+        .describe("The billing account that made the purchase. Renewals of a project subscription are charged to the project's current billing account."),
+    account: AccountIdentity,
+    product_id: ProductID,
+    project_id: zod
+        .uuid()
+        .nullish()
+        .describe("Which project this is for. Absent when it was bought at account level, such as a\nmembership, which belongs to no single project."),
+    project: zod
+        .union([NamedIdentity, zod.null()])
+        .optional()
+        .describe("The project and its current name, for display. Absent for a purchase at account level,\nand when the project no longer exists or its details cannot be read at the moment;\n`project_id` still identifies it then."),
+    product: Product,
+    plan_id: zod.uuid(),
+    plan_name: zod.string(),
+    price_id: zod.uuid(),
+    quantity: zod.string(),
+    current_term_end: zod.iso
+        .datetime({ offset: true })
+        .nullish()
+        .describe("When a prepaid subscription renews or expires, the end of the last service period bought.\nRenewing several periods in advance moves it. Null until a new subscription becomes active, even when\nits purchase has been paid, and for postpaid subscriptions."),
+    current_period_start: zod.iso
+        .datetime({ offset: true })
+        .nullish()
+        .describe("Start of the service period in effect now. Null when none is, including for postpaid subscriptions."),
+    current_period_end: zod.iso
+        .datetime({ offset: true })
+        .nullish()
+        .describe("End of the service period in effect now. Renewing in advance moves `current_term_end`, not\nthis. Null when no period is in effect, including for postpaid subscriptions."),
+    auto_renew: zod
+        .boolean()
+        .describe("A prepaid subscription renews automatically while this is on. A postpaid subscription always continues until it is canceled; this is true until a cancellation is requested and cannot be set."),
+    status: zod
+        .enum(["pending", "provisioning", "active", "suspended", "canceled", "terminated"])
+        .describe("pending means the purchase relationship exists but its order has not been accepted.\nprovisioning means the service accepted the order and is delivering. For a service-owned\npurchase, only confirmed delivery moves it to active; paying alone does not.\ncanceled means cancellation completed, or an unfulfilled purchase was canceled or failed without delivery.\nterminated means an administrator or the owning service immediately ended the commercial relationship."),
+    started_at: zod.iso
+        .datetime({ offset: true })
+        .nullish()
+        .describe("Confirmed start of service. Null until a new subscription becomes active, including after payment."),
+    ended_at: zod.iso.datetime({ offset: true }).nullish(),
+})
+    .describe("An independently billed purchase relationship, separate from the owning service's resource.\nPlacing a new prepaid or postpaid service order creates a pending subscription for each line\nin the same purchase transaction. Its ID is returned on the order item and remains stable\nthrough checkout and delivery. One order may create several subscriptions, such as an instance,\nits system disk and its address; it has no single subscription ID.\n\nPending and provisioning do not grant service or accrue usage. A service-owned subscription\nbecomes provisioning when the owning service accepts the order, and active when the service\nconfirms delivery, with started_at set to the confirmed effective time; payment changes neither. Prepaid service periods start\nthen; postpaid usage starts only when the service reports actual delivery and metering.\n\nOne-time delivery may omit a subscription. Renewals reference and extend existing subscriptions\nrather than creating another; a change keeps the subscription ID and switches its terms when it\ntakes effect. Canceling or failing an unfulfilled purchase sets its pending or provisioning\nsubscriptions to canceled without starting a service period.\nFixed renewals use the agreed recurring_amount and interval; already paid periods retain their\noriginal value. Technical state belongs to the owning service.\n\nA purchased shared capacity limit, such as a regional snapshot count quota, can have its own\nsubscription. Activating that capacity confirms delivery of the quota, not individual snapshots.\nCreating or deleting snapshots within it does not create, activate or terminate more subscriptions;\nthe owning service enforces current holdings against the purchased count.");

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

@@ -0,0 +1,53 @@
+/**
+ * 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 SubscriptionCancellation: zod.ZodObject<{
+    reason: zod.ZodOptional<zod.ZodString>;
+    cancellation_id: zod.ZodOptional<zod.ZodUUID>;
+    id: zod.ZodUUID;
+    subscription_id: zod.ZodUUID;
+    status: zod.ZodEnum<{
+        completed: "completed";
+        failed: "failed";
+        requested: "requested";
+        scheduled: "scheduled";
+        releasing: "releasing";
+        canceled: "canceled";
+    }>;
+    mode: zod.ZodEnum<{
+        immediate: "immediate";
+        period_end: "period_end";
+    }>;
+    requested_at: zod.z.ZodISODateTime;
+    scheduled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+    effective_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+    completed_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+    release_started_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+    canceled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+    forfeit_remaining_value: zod.ZodBoolean;
+    failure_code: zod.ZodOptional<zod.ZodString>;
+    failure_reason: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type SubscriptionCancellation = zod.input<typeof SubscriptionCancellation>;
+export type SubscriptionCancellationOutput = zod.output<typeof SubscriptionCancellation>;

package/dist/compute/v1/generated/validators/subscriptionCancellation.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";
+export const SubscriptionCancellation = zod
+    .strictObject({
+    reason: zod.string().optional(),
+    cancellation_id: zod
+        .uuid()
+        .optional()
+        .describe("The cancellation this request belongs to, with the other subscriptions released together."),
+    id: zod.uuid(),
+    subscription_id: zod.uuid(),
+    status: zod.enum(["requested", "scheduled", "releasing", "failed", "completed", "canceled"]),
+    mode: zod.enum(["immediate", "period_end"]),
+    requested_at: zod.iso.datetime({ offset: true }),
+    scheduled_at: zod.iso.datetime({ offset: true }).optional(),
+    effective_at: zod.iso.datetime({ offset: true }).optional(),
+    completed_at: zod.iso.datetime({ offset: true }).optional(),
+    release_started_at: zod.iso.datetime({ offset: true }).optional(),
+    canceled_at: zod.iso.datetime({ offset: true }).optional(),
+    forfeit_remaining_value: zod.boolean(),
+    failure_code: zod.string().optional(),
+    failure_reason: zod.string().optional(),
+})
+    .describe("The latest cancellation that includes the subscription, with this subscription's item. `id` is the\nitem; `cancellation_id` is the cancellation. scheduled_at is the intended time; effective_at is the\nconfirmed end of service. A cancellation alone does not stop metering or issue a refund.");

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

@@ -0,0 +1,133 @@
+/**
+ * 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 SubscriptionList: zod.ZodObject<{
+    items: zod.ZodArray<zod.ZodObject<{
+        currency: zod.ZodString;
+        charge_type: zod.ZodEnum<{
+            postpaid: "postpaid";
+            prepaid: "prepaid";
+            one_time: "one_time";
+        }>;
+        interval: zod.ZodEnum<{
+            none: "none";
+            day: "day";
+            month: "month";
+            year: "year";
+        }>;
+        interval_count: zod.ZodOptional<zod.ZodInt>;
+        recurring_amount: zod.ZodOptional<zod.ZodString>;
+        termination_policy: zod.ZodOptional<zod.ZodEnum<{
+            immediate: "immediate";
+            period_end: "period_end";
+        }>>;
+        refund_policy: zod.ZodOptional<zod.ZodEnum<{
+            none: "none";
+            prorated: "prorated";
+        }>>;
+        order_item_id: zod.ZodOptional<zod.ZodUUID>;
+        replaces_subscription_id: zod.ZodOptional<zod.ZodUUID>;
+        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>>;
+        discounted_renewals_remaining: zod.ZodOptional<zod.ZodInt>;
+        suspend_reason: zod.ZodOptional<zod.ZodString>;
+        billing_cycle_anchor: zod.ZodOptional<zod.z.ZodISODateTime>;
+        cancellation: zod.ZodOptional<zod.ZodObject<{
+            reason: zod.ZodOptional<zod.ZodString>;
+            cancellation_id: zod.ZodOptional<zod.ZodUUID>;
+            id: zod.ZodUUID;
+            subscription_id: zod.ZodUUID;
+            status: zod.ZodEnum<{
+                completed: "completed";
+                failed: "failed";
+                requested: "requested";
+                scheduled: "scheduled";
+                releasing: "releasing";
+                canceled: "canceled";
+            }>;
+            mode: zod.ZodEnum<{
+                immediate: "immediate";
+                period_end: "period_end";
+            }>;
+            requested_at: zod.z.ZodISODateTime;
+            scheduled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+            effective_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+            completed_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+            release_started_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+            canceled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+            forfeit_remaining_value: zod.ZodBoolean;
+            failure_code: zod.ZodOptional<zod.ZodString>;
+            failure_reason: zod.ZodOptional<zod.ZodString>;
+        }, zod.z.core.$strict>>;
+        default_payment_method_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
+        created_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+        id: zod.ZodUUID;
+        billing_account_id: zod.ZodInt;
+        account: zod.ZodObject<{
+            id: zod.ZodInt;
+            name: zod.ZodString;
+            currency: zod.ZodString;
+        }, zod.z.core.$strict>;
+        product_id: zod.ZodString;
+        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]>>;
+        product: 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;
+        price_id: zod.ZodUUID;
+        quantity: zod.ZodString;
+        current_term_end: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+        current_period_start: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+        current_period_end: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+        auto_renew: zod.ZodBoolean;
+        status: zod.ZodEnum<{
+            pending: "pending";
+            active: "active";
+            suspended: "suspended";
+            canceled: "canceled";
+            provisioning: "provisioning";
+            terminated: "terminated";
+        }>;
+        started_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+        ended_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+    }, 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 SubscriptionList = zod.input<typeof SubscriptionList>;
+export type SubscriptionListOutput = zod.output<typeof SubscriptionList>;

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

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