@leaflow/sdk 0.212.0 → 0.214.0

package/dist/billing/v1/generated/validators/quoteRequest.zod.d.ts

@@ -1,101 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Billing API
- * Products, prices, orders, subscriptions and account billing. Operations on a billing account require an account access token. The account, its balance, payment options and quotes are also readable by members of the projects it currently pays for; changing the account and moving its funds need the owner. Members of a project, as each operation states, can also read the project's billing account, subscriptions and orders, complete and pay for its purchases, quote purchases, changes and renewals, preview cancellations, and, with the project permission `billing:finance.manage` granted in IAM, renew, cancel and turn automatic renewal of its subscriptions on or off, change its billing account and read its costs. A member without the permission an operation needs is refused with 403 `PERMISSION_DENIED` and `meta.permission`; a caller who is not a member, with 403 `IAM_NOT_PROJECT_MEMBER`. Public catalogue operations declare no security requirement.
- * OpenAPI spec version: v1
- */
-import * as zod from "zod";
-export declare const quoteRequestCurrencyMin = 3;
-export declare const quoteRequestCurrencyMax = 3;
-export declare const quoteRequestItemsMax = 100;
-export declare const quoteRequestRenewalsMax = 100;
-export declare const quoteRequestChangesMax = 100;
-export declare const quoteRequestPromotionCodeMax = 64;
-export declare const QuoteRequest: zod.ZodObject<{
-    billing_account_id: zod.ZodOptional<zod.ZodInt>;
-    currency: zod.ZodOptional<zod.ZodString>;
-    items: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
-        price_lookup_key: zod.ZodOptional<zod.ZodString>;
-        plan_lookup_key: zod.ZodOptional<zod.ZodString>;
-        price_id: zod.ZodOptional<zod.ZodUUID>;
-        product_id: zod.ZodOptional<zod.ZodString>;
-        plan_id: zod.ZodOptional<zod.ZodUUID>;
-        price_type: zod.ZodOptional<zod.ZodEnum<{
-            one_time: "one_time";
-            recurring: "recurring";
-        }>>;
-        usage_type: zod.ZodOptional<zod.ZodEnum<{
-            licensed: "licensed";
-            metered: "metered";
-        }>>;
-        interval: zod.ZodOptional<zod.ZodEnum<{
-            none: "none";
-            day: "day";
-            month: "month";
-            year: "year";
-        }>>;
-        interval_count: zod.ZodOptional<zod.ZodInt>;
-        cancellation_policy: zod.ZodOptional<zod.ZodEnum<{
-            immediate: "immediate";
-            period_end: "period_end";
-        }>>;
-        quantity: zod.ZodString;
-        dimensions: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
-    }, zod.z.core.$strict>>>;
-    renewals: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
-        subscription_id: zod.ZodUUID;
-        price_id: zod.ZodOptional<zod.ZodUUID>;
-        interval: zod.ZodOptional<zod.ZodEnum<{
-            day: "day";
-            month: "month";
-            year: "year";
-        }>>;
-        interval_count: zod.ZodOptional<zod.ZodInt>;
-        cancellation_policy: zod.ZodOptional<zod.ZodEnum<{
-            immediate: "immediate";
-            period_end: "period_end";
-        }>>;
-        periods: zod.ZodDefault<zod.ZodInt>;
-    }, zod.z.core.$strict>>>;
-    changes: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
-        subscription_id: zod.ZodUUID;
-        price_lookup_key: zod.ZodOptional<zod.ZodString>;
-        plan_lookup_key: zod.ZodOptional<zod.ZodString>;
-        price_id: zod.ZodOptional<zod.ZodUUID>;
-        product_id: zod.ZodOptional<zod.ZodString>;
-        plan_id: zod.ZodOptional<zod.ZodUUID>;
-        price_type: zod.ZodOptional<zod.ZodEnum<{
-            one_time: "one_time";
-            recurring: "recurring";
-        }>>;
-        usage_type: zod.ZodOptional<zod.ZodEnum<{
-            licensed: "licensed";
-            metered: "metered";
-        }>>;
-        interval: zod.ZodOptional<zod.ZodEnum<{
-            none: "none";
-            day: "day";
-            month: "month";
-            year: "year";
-        }>>;
-        interval_count: zod.ZodOptional<zod.ZodInt>;
-        cancellation_policy: zod.ZodOptional<zod.ZodEnum<{
-            immediate: "immediate";
-            period_end: "period_end";
-        }>>;
-        quantity: zod.ZodString;
-        dimensions: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
-    }, zod.z.core.$strict>>>;
-    change_effective: zod.ZodOptional<zod.ZodEnum<{
-        immediate: "immediate";
-        period_end: "period_end";
-    }>>;
-    address: zod.ZodOptional<zod.ZodObject<{
-        country: zod.ZodString;
-        state: zod.ZodOptional<zod.ZodString>;
-    }, zod.z.core.$strict>>;
-    promotion_code: zod.ZodOptional<zod.ZodString>;
-}, zod.z.core.$strict>;
-export type QuoteRequest = zod.input<typeof QuoteRequest>;
-export type QuoteRequestOutput = zod.output<typeof QuoteRequest>;

package/dist/billing/v1/generated/validators/quoteRequest.zod.js

@@ -1,57 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Billing API
- * Products, prices, orders, subscriptions and account billing. Operations on a billing account require an account access token. The account, its balance, payment options and quotes are also readable by members of the projects it currently pays for; changing the account and moving its funds need the owner. Members of a project, as each operation states, can also read the project's billing account, subscriptions and orders, complete and pay for its purchases, quote purchases, changes and renewals, preview cancellations, and, with the project permission `billing:finance.manage` granted in IAM, renew, cancel and turn automatic renewal of its subscriptions on or off, change its billing account and read its costs. A member without the permission an operation needs is refused with 403 `PERMISSION_DENIED` and `meta.permission`; a caller who is not a member, with 403 `IAM_NOT_PROJECT_MEMBER`. Public catalogue operations declare no security requirement.
- * OpenAPI spec version: v1
- */
-import * as zod from "zod";
-import { QuoteAddress } from "./quoteAddress.zod.js";
-import { QuoteChangeInput } from "./quoteChangeInput.zod.js";
-import { QuoteItemInput } from "./quoteItemInput.zod.js";
-import { QuoteRenewal } from "./quoteRenewal.zod.js";
-export const quoteRequestCurrencyMin = 3;
-export const quoteRequestCurrencyMax = 3;
-export const quoteRequestItemsMax = 100;
-export const quoteRequestRenewalsMax = 100;
-export const quoteRequestChangesMax = 100;
-export const quoteRequestPromotionCodeMax = 64;
-export const QuoteRequest = zod
-    .strictObject({
-    billing_account_id: zod
-        .int()
-        .min(1)
-        .optional()
-        .describe("The billing account to price for; it must be yours or currently pay for a project you are a member of, and an access token is required. Renewals must currently be paid by it."),
-    currency: zod
-        .string()
-        .min(quoteRequestCurrencyMin)
-        .max(quoteRequestCurrencyMax)
-        .optional()
-        .describe("The ISO 4217 currency to price in without an account."),
-    items: zod
-        .array(QuoteItemInput)
-        .min(1)
-        .max(quoteRequestItemsMax)
-        .optional()
-        .describe("A proposed purchase."),
-    renewals: zod
-        .array(QuoteRenewal)
-        .min(1)
-        .max(quoteRequestRenewalsMax)
-        .optional()
-        .describe("Preview renewing these subscriptions, each at most once; each entry is a separate renewal order. Each must currently be paid by `billing_account_id` and be yours to read, as the owner of that account or a member of the subscription's project. To apply a promotion code, create a renewal Checkout Session and quote it."),
-    changes: zod
-        .array(QuoteChangeInput)
-        .min(1)
-        .max(quoteRequestChangesMax)
-        .optional()
-        .describe("Preview changing these subscriptions in one order, each at most once. Each must currently be paid by `billing_account_id` and be yours to read, as the owner of that account or a member of the subscription's project; all must belong to the same project, or all to no project."),
-    change_effective: zod
-        .enum(["immediate", "period_end"])
-        .optional()
-        .describe("When the changes take effect; defaults to `immediate`. `immediate` prices the rest of the paid period from `proration_date`, charging an upgrade the difference and showing what a downgrade refunds. `period_end` prices the first period at the new terms, which replaces the renewal when the paid period ends."),
-    address: QuoteAddress.optional().describe("Only with `currency`. Where the customer is, to include the tax that would be added there for a customer who is not tax exempt; `tax_status` is then `complete`. Refused with `billing_account_id`, whose invoice contact decides tax."),
-    promotion_code: zod.string().min(1).max(quoteRequestPromotionCodeMax).optional(),
-})
-    .describe("Quote proposed items, changes or renewals: exactly one of them. Give exactly one of `billing_account_id` and `currency`; changes and renewals need the account. Promotion codes apply to proposed items and changes. An invalid combination fails with `BILLING_PURCHASE_INVALID` and the field.");

package/dist/billing/v1/generated/validators/quotedDiscount.zod.d.ts

@@ -1,29 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Billing API
- * Products, prices, orders, subscriptions and account billing. Operations on a billing account require an account access token. The account, its balance, payment options and quotes are also readable by members of the projects it currently pays for; changing the account and moving its funds need the owner. Members of a project, as each operation states, can also read the project's billing account, subscriptions and orders, complete and pay for its purchases, quote purchases, changes and renewals, preview cancellations, and, with the project permission `billing:finance.manage` granted in IAM, renew, cancel and turn automatic renewal of its subscriptions on or off, change its billing account and read its costs. A member without the permission an operation needs is refused with 403 `PERMISSION_DENIED` and `meta.permission`; a caller who is not a member, with 403 `IAM_NOT_PROJECT_MEMBER`. Public catalogue operations declare no security requirement.
- * OpenAPI spec version: v1
- */
-import * as zod from "zod";
-export declare const quotedDiscountPromotionCodeMax = 64;
-export declare const QuotedDiscount: zod.ZodObject<{
-    type: zod.ZodEnum<{
-        promotion_code: "promotion_code";
-        account_discount: "account_discount";
-    }>;
-    name: zod.ZodString;
-    promotion_code: zod.ZodNullable<zod.ZodString>;
-    frequency: zod.ZodEnum<{
-        recurring: "recurring";
-        once: "once";
-        forever: "forever";
-    }>;
-    frequency_duration: zod.ZodNullable<zod.ZodInt>;
-    eligibility: zod.ZodEnum<{
-        confirmed: "confirmed";
-        unverified: "unverified";
-    }>;
-}, zod.z.core.$strict>;
-export type QuotedDiscount = zod.input<typeof QuotedDiscount>;
-export type QuotedDiscountOutput = zod.output<typeof QuotedDiscount>;

package/dist/billing/v1/generated/validators/quotedDiscount.zod.js

@@ -1,32 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Billing API
- * Products, prices, orders, subscriptions and account billing. Operations on a billing account require an account access token. The account, its balance, payment options and quotes are also readable by members of the projects it currently pays for; changing the account and moving its funds need the owner. Members of a project, as each operation states, can also read the project's billing account, subscriptions and orders, complete and pay for its purchases, quote purchases, changes and renewals, preview cancellations, and, with the project permission `billing:finance.manage` granted in IAM, renew, cancel and turn automatic renewal of its subscriptions on or off, change its billing account and read its costs. A member without the permission an operation needs is refused with 403 `PERMISSION_DENIED` and `meta.permission`; a caller who is not a member, with 403 `IAM_NOT_PROJECT_MEMBER`. Public catalogue operations declare no security requirement.
- * OpenAPI spec version: v1
- */
-import * as zod from "zod";
-export const quotedDiscountPromotionCodeMax = 64;
-export const QuotedDiscount = zod
-    .strictObject({
-    type: zod.enum(["promotion_code", "account_discount"]),
-    name: zod.string(),
-    promotion_code: zod
-        .string()
-        .min(1)
-        .max(quotedDiscountPromotionCodeMax)
-        .nullable()
-        .describe("Code text for a promotion_code discount; null for an account_discount."),
-    frequency: zod
-        .enum(["once", "recurring", "forever"])
-        .describe("Whether the discount continues on renewals of what is bought: `once` applies only to this purchase, `recurring` for `frequency_duration` periods including the first, `forever` on every renewal."),
-    frequency_duration: zod
-        .int()
-        .min(1)
-        .nullable()
-        .describe("For `recurring`, the periods the discount lasts; null otherwise."),
-    eligibility: zod
-        .enum(["confirmed", "unverified"])
-        .describe("`confirmed`: every condition of the discount holds for the billing account. `unverified`: a quote without an account, where conditions that depend on the account, such as a first purchase or a per-account limit, are checked only when a Checkout Session is completed."),
-})
-    .describe("The discount selected for this calculation, not applied and not reserved. Amounts are on the quote and its lines.");

package/dist/billing/v1/generated/validators/renewalPrice.zod.d.ts

@@ -1,33 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Billing API
- * Products, prices, orders, subscriptions and account billing. Operations on a billing account require an account access token. The account, its balance, payment options and quotes are also readable by members of the projects it currently pays for; changing the account and moving its funds need the owner. Members of a project, as each operation states, can also read the project's billing account, subscriptions and orders, complete and pay for its purchases, quote purchases, changes and renewals, preview cancellations, and, with the project permission `billing:finance.manage` granted in IAM, renew, cancel and turn automatic renewal of its subscriptions on or off, change its billing account and read its costs. A member without the permission an operation needs is refused with 403 `PERMISSION_DENIED` and `meta.permission`; a caller who is not a member, with 403 `IAM_NOT_PROJECT_MEMBER`. Public catalogue operations declare no security requirement.
- * OpenAPI spec version: v1
- */
-import * as zod from "zod";
-export declare const RenewalPrice: zod.ZodObject<{
-    cancellation_policy: zod.ZodOptional<zod.ZodEnum<{
-        immediate: "immediate";
-        period_end: "period_end";
-    }>>;
-    refund_policy: zod.ZodOptional<zod.ZodEnum<{
-        none: "none";
-        prorated: "prorated";
-        short_rate: "short_rate";
-    }>>;
-    short_rate_multiplier: zod.ZodOptional<zod.ZodString>;
-    short_rate_threshold_seconds: zod.ZodOptional<zod.ZodInt>;
-    price_id: zod.ZodUUID;
-    interval_count: zod.ZodInt;
-    interval: zod.ZodEnum<{
-        day: "day";
-        month: "month";
-        year: "year";
-    }>;
-    amount: zod.ZodOptional<zod.ZodString>;
-    currency: zod.ZodOptional<zod.ZodString>;
-    current: zod.ZodBoolean;
-}, zod.z.core.$strict>;
-export type RenewalPrice = zod.input<typeof RenewalPrice>;
-export type RenewalPriceOutput = zod.output<typeof RenewalPrice>;

package/dist/billing/v1/generated/validators/renewalPrice.zod.js

@@ -1,25 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Billing API
- * Products, prices, orders, subscriptions and account billing. Operations on a billing account require an account access token. The account, its balance, payment options and quotes are also readable by members of the projects it currently pays for; changing the account and moving its funds need the owner. Members of a project, as each operation states, can also read the project's billing account, subscriptions and orders, complete and pay for its purchases, quote purchases, changes and renewals, preview cancellations, and, with the project permission `billing:finance.manage` granted in IAM, renew, cancel and turn automatic renewal of its subscriptions on or off, change its billing account and read its costs. A member without the permission an operation needs is refused with 403 `PERMISSION_DENIED` and `meta.permission`; a caller who is not a member, with 403 `IAM_NOT_PROJECT_MEMBER`. Public catalogue operations declare no security requirement.
- * OpenAPI spec version: v1
- */
-import * as zod from "zod";
-import { CancellationPolicy } from "./cancellationPolicy.zod.js";
-import { Money } from "./money.zod.js";
-import { RefundPolicy } from "./refundPolicy.zod.js";
-export const RenewalPrice = zod.strictObject({
-    cancellation_policy: CancellationPolicy.optional(),
-    refund_policy: RefundPolicy.optional(),
-    short_rate_multiplier: zod.string().optional().describe("Refund policy `short_rate` only."),
-    short_rate_threshold_seconds: zod.int().optional().describe("Refund policy `short_rate` only."),
-    price_id: zod.uuid(),
-    interval_count: zod.int().describe("How many periods one renewal covers."),
-    interval: zod.enum(["day", "month", "year"]),
-    amount: Money.optional().describe("What renewing for this term costs, for the quantity held."),
-    currency: zod.string().optional(),
-    current: zod
-        .boolean()
-        .describe("The term the subscription renews at now; renewing for it keeps the agreed price."),
-});

package/dist/billing/v1/generated/validators/renewalPriceList.zod.d.ts

@@ -1,40 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Billing API
- * Products, prices, orders, subscriptions and account billing. Operations on a billing account require an account access token. The account, its balance, payment options and quotes are also readable by members of the projects it currently pays for; changing the account and moving its funds need the owner. Members of a project, as each operation states, can also read the project's billing account, subscriptions and orders, complete and pay for its purchases, quote purchases, changes and renewals, preview cancellations, and, with the project permission `billing:finance.manage` granted in IAM, renew, cancel and turn automatic renewal of its subscriptions on or off, change its billing account and read its costs. A member without the permission an operation needs is refused with 403 `PERMISSION_DENIED` and `meta.permission`; a caller who is not a member, with 403 `IAM_NOT_PROJECT_MEMBER`. Public catalogue operations declare no security requirement.
- * OpenAPI spec version: v1
- */
-import * as zod from "zod";
-export declare const RenewalPriceList: zod.ZodObject<{
-    items: zod.ZodArray<zod.ZodObject<{
-        cancellation_policy: zod.ZodOptional<zod.ZodEnum<{
-            immediate: "immediate";
-            period_end: "period_end";
-        }>>;
-        refund_policy: zod.ZodOptional<zod.ZodEnum<{
-            none: "none";
-            prorated: "prorated";
-            short_rate: "short_rate";
-        }>>;
-        short_rate_multiplier: zod.ZodOptional<zod.ZodString>;
-        short_rate_threshold_seconds: zod.ZodOptional<zod.ZodInt>;
-        price_id: zod.ZodUUID;
-        interval_count: zod.ZodInt;
-        interval: zod.ZodEnum<{
-            day: "day";
-            month: "month";
-            year: "year";
-        }>;
-        amount: zod.ZodOptional<zod.ZodString>;
-        currency: zod.ZodOptional<zod.ZodString>;
-        current: zod.ZodBoolean;
-    }, 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 RenewalPriceList = zod.input<typeof RenewalPriceList>;
-export type RenewalPriceListOutput = zod.output<typeof RenewalPriceList>;

package/dist/billing/v1/generated/validators/renewalPriceList.zod.js

@@ -1,14 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Billing API
- * Products, prices, orders, subscriptions and account billing. Operations on a billing account require an account access token. The account, its balance, payment options and quotes are also readable by members of the projects it currently pays for; changing the account and moving its funds need the owner. Members of a project, as each operation states, can also read the project's billing account, subscriptions and orders, complete and pay for its purchases, quote purchases, changes and renewals, preview cancellations, and, with the project permission `billing:finance.manage` granted in IAM, renew, cancel and turn automatic renewal of its subscriptions on or off, change its billing account and read its costs. A member without the permission an operation needs is refused with 403 `PERMISSION_DENIED` and `meta.permission`; a caller who is not a member, with 403 `IAM_NOT_PROJECT_MEMBER`. Public catalogue operations declare no security requirement.
- * OpenAPI spec version: v1
- */
-import * as zod from "zod";
-import { OffsetPagination } from "./offsetPagination.zod.js";
-import { RenewalPrice } from "./renewalPrice.zod.js";
-export const RenewalPriceList = zod.strictObject({
-    items: zod.array(RenewalPrice),
-    pagination: OffsetPagination,
-});

package/dist/billing/v1/generated/validators/subscriptionCancellation.zod.js

@@ -1,31 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Billing API
- * Products, prices, orders, subscriptions and account billing. Operations on a billing account require an account access token. The account, its balance, payment options and quotes are also readable by members of the projects it currently pays for; changing the account and moving its funds need the owner. Members of a project, as each operation states, can also read the project's billing account, subscriptions and orders, complete and pay for its purchases, quote purchases, changes and renewals, preview cancellations, and, with the project permission `billing:finance.manage` granted in IAM, renew, cancel and turn automatic renewal of its subscriptions on or off, change its billing account and read its costs. A member without the permission an operation needs is refused with 403 `PERMISSION_DENIED` and `meta.permission`; a caller who is not a member, with 403 `IAM_NOT_PROJECT_MEMBER`. Public catalogue operations declare no security requirement.
- * OpenAPI spec version: v1
- */
-import * as zod from "zod";
-import { CancellationMode } from "./cancellationMode.zod.js";
-export const SubscriptionCancellation = zod
-    .strictObject({
-    reason: zod.string().optional(),
-    cancellation_id: zod
-        .uuid()
-        .optional()
-        .describe("The cancellation this item 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: CancellationMode,
-    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 including the subscription, with this subscription's item: `id` is the item and `cancellation_id` the cancellation. scheduled_at is the intended time and effective_at the confirmed end of service.");

package/dist/compute/v2/generated/validators/elasticIPAssociationID.zod.d.ts

@@ -1,41 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Compute API
- * Leaflow Compute user API for managing instances, volumes, snapshots, volume backups, public and private images, virtual private clouds, subnets, routes, security groups, network interfaces and elastic IPs.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `scopedTokenAuth` security scheme. The catalog reads, which list and retrieve regions, availability zones, instance types, volume types, public images and elastic IP lines, also answer without a token, so a visitor can configure a purchase and price it with Billing before signing in. A token given to them is still verified, and an invalid one is refused.
- *
- * ## Conventions
- *
- * - **Purchases.** A purchase that creates resources returns them together with the `checkout_session_id` of its Billing Checkout Session and, once checkout completes, its `order_id`. They are readable at once and start as `pending`: checkout may not be complete, 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, the resource is created: it stays `pending`, then reaches its usual status, such as `running` or `available`. When the Checkout Session expires, 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. A purchased change, such as a resize requested with `instance_type_id`, `size_gib` or `bandwidth_mbps` on the resource, returns the resource unchanged with the Checkout Session for the change, and applies once its order is accepted.
- * - **Commercial terms.** Compute catalogs describe technical specifications and, for each order line a purchase makes, how it is sold in Billing (a `BillingComponent`: its Plan, dimensions, what its quantity counts and what its meters read); prices, amounts and currency belong to Billing. A purchase chooses its terms with `billing`, and Billing selects the matching price. Read prices and their rates with Billing's `search-prices` from those components, quote a proposed purchase with `get-quote`, and a change of a resource by its `subscription_id`; Compute has no quote or price proxy endpoint and returns no amounts.
- * - **Checkout.** `checkout` is passed to Billing unchanged. Omit it for automatic checkout, which completes checkout within the request and pays from eligible credit grants and balance; 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` with an open Checkout Session and no order, even for a zero total; nothing is created until the customer completes checkout in Billing, where a promotion code can be applied, and the order is paid. Do not submit the purchase again after paying; after an uncertain response, look the Checkout Session up in Billing first.
- * - **Quotas.** A creation, purchase or resize that adds to what a project holds in a region is checked against the project's quota there before anything is ordered or created, and is refused with HTTP 409 `COMPUTE_PROJECT_QUOTA_EXCEEDED`, whose `meta` names the `resource`, its `limit`, the amount `used` and the amount `requested`. An instance purchase counts the volumes, the new primary network interface and the new elastic IP bought with each instance. Read the limits with `list-quotas`; a limit no operator set is the platform default.
- * - **Projects.** Resource ownership and project identifiers refer to IAM platform projects, not OpenStack tenants. Instances, images and networks share one infrastructure OpenStack project; the platform project remains the authorization and ownership boundary.
- * - **Custom methods.** An action that is not one of the standard methods (list, get, create, update, delete) is a custom method, `POST` on the resource's path followed by `:` and the verb, as in `POST /api/v2/instances/{id}:reboot` (AIP-136). A state is changed by its custom method, never by writing the state: `:start` and `:stop`, `:rescue` and `:unrescue`, `:associate` and `:disassociate`.
- * - **Operations.** Requests such as `:start`, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `status` names it, as in `starting` or `deleting`; once it has finished the resource shows its new status and 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 volume, is refused when either has one. A purchased change, such as a resize, is an operation from the moment its Checkout Session is created until the change is applied, the session expires or its order is canceled. Renaming and replacing labels or notes are not operations and are accepted at any time. **Updating.** A `PATCH` carries only mutable fields, all optional and at least one given, and answers 200 when only descriptive fields changed and 202 when an operation started. An operational field (`instance_type_id`, `size_gib`, `bandwidth_mbps`) cannot be combined with any other field in the same request: it is refused with 422 `UPDATE_FIELDS_COMBINED`, because a rename that committed beside a change that was then refused would leave the request half applied.
- * - **Billing relationships.** A purchased resource records its `checkout_session_id` and, once checkout completes, its `order_id`, `order_item_id` and `subscription_id`. Its `access_state` is `pending` until the order is accepted and delivery settles it, then `enabled`; a subscription that lapses suspends or reclaims the resource it pays for. Deleting a resource that subscriptions pay for cancels the subscriptions of its `release_set` in Billing, and the deletion answers with that cancellation.
- * - **Availability zones.** A volume and an instance must reside in the same availability zone to be attached. An instance type and a volume type each belong to one availability zone, as on GCP, so a purchase names the type and the type names the zone; the volumes bought with an instance have to be of types of the instance type's zone.
- * - **IPv6 is routed, not translated.** A virtual private cloud with IPv6 holds a /56 and each of its subnets a /64 of it, as on Alibaba Cloud, Tencent Cloud and Azure; IPv6 and its security groups require no EIP or NAT gateway. EIP and NATGateway are IPv4 products; IPv6 EIP, NAT66 and IPv6 port forwarding are not supported.
- * - **Elastic IP release.** A released address returns to available inventory as soon as its cleanup is confirmed, with no cooldown period. Removing or replacing an elastic IP's association keeps the address held by the project and does not release it.
- * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
- *
- * ## Resource identifiers
- *
- * Compute resource IDs use the fixed TypeID prefix declared in their schema. UUID text is not accepted for these resource IDs. Project, order, subscription and Billing Plan identifiers remain UUIDs. Historical operation-log subject IDs are audit facts and are not rewritten.
- *
- * ## Error meta
- *
- * Resource identifiers in an error's `meta` (`resource_id`, `volume_id`, `network_interface_id` and the like) are TypeIDs, in the same form as the identifiers in resources. `meta.resource_type` is the resource's name as written in paths, with underscores: `instance`, `volume`, `elastic_ip`, `network_interface`, `virtual_private_cloud`, `private_image`, `volume_backup`, and so on.
- * OpenAPI spec version: 2.0.0
- */
-import * as zod from "zod";
-export declare const ElasticIPAssociationIDMin = 41;
-export declare const ElasticIPAssociationIDMax = 41;
-export declare const ElasticIPAssociationIDRegExp: RegExp;
-export declare const ElasticIPAssociationID: zod.ZodString;
-export type ElasticIPAssociationID = zod.input<typeof ElasticIPAssociationID>;
-export type ElasticIPAssociationIDOutput = zod.output<typeof ElasticIPAssociationID>;

package/dist/compute/v2/generated/validators/elasticIPAssociationID.zod.js

@@ -1,44 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Compute API
- * Leaflow Compute user API for managing instances, volumes, snapshots, volume backups, public and private images, virtual private clouds, subnets, routes, security groups, network interfaces and elastic IPs.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `scopedTokenAuth` security scheme. The catalog reads, which list and retrieve regions, availability zones, instance types, volume types, public images and elastic IP lines, also answer without a token, so a visitor can configure a purchase and price it with Billing before signing in. A token given to them is still verified, and an invalid one is refused.
- *
- * ## Conventions
- *
- * - **Purchases.** A purchase that creates resources returns them together with the `checkout_session_id` of its Billing Checkout Session and, once checkout completes, its `order_id`. They are readable at once and start as `pending`: checkout may not be complete, 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, the resource is created: it stays `pending`, then reaches its usual status, such as `running` or `available`. When the Checkout Session expires, 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. A purchased change, such as a resize requested with `instance_type_id`, `size_gib` or `bandwidth_mbps` on the resource, returns the resource unchanged with the Checkout Session for the change, and applies once its order is accepted.
- * - **Commercial terms.** Compute catalogs describe technical specifications and, for each order line a purchase makes, how it is sold in Billing (a `BillingComponent`: its Plan, dimensions, what its quantity counts and what its meters read); prices, amounts and currency belong to Billing. A purchase chooses its terms with `billing`, and Billing selects the matching price. Read prices and their rates with Billing's `search-prices` from those components, quote a proposed purchase with `get-quote`, and a change of a resource by its `subscription_id`; Compute has no quote or price proxy endpoint and returns no amounts.
- * - **Checkout.** `checkout` is passed to Billing unchanged. Omit it for automatic checkout, which completes checkout within the request and pays from eligible credit grants and balance; 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` with an open Checkout Session and no order, even for a zero total; nothing is created until the customer completes checkout in Billing, where a promotion code can be applied, and the order is paid. Do not submit the purchase again after paying; after an uncertain response, look the Checkout Session up in Billing first.
- * - **Quotas.** A creation, purchase or resize that adds to what a project holds in a region is checked against the project's quota there before anything is ordered or created, and is refused with HTTP 409 `COMPUTE_PROJECT_QUOTA_EXCEEDED`, whose `meta` names the `resource`, its `limit`, the amount `used` and the amount `requested`. An instance purchase counts the volumes, the new primary network interface and the new elastic IP bought with each instance. Read the limits with `list-quotas`; a limit no operator set is the platform default.
- * - **Projects.** Resource ownership and project identifiers refer to IAM platform projects, not OpenStack tenants. Instances, images and networks share one infrastructure OpenStack project; the platform project remains the authorization and ownership boundary.
- * - **Custom methods.** An action that is not one of the standard methods (list, get, create, update, delete) is a custom method, `POST` on the resource's path followed by `:` and the verb, as in `POST /api/v2/instances/{id}:reboot` (AIP-136). A state is changed by its custom method, never by writing the state: `:start` and `:stop`, `:rescue` and `:unrescue`, `:associate` and `:disassociate`.
- * - **Operations.** Requests such as `:start`, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `status` names it, as in `starting` or `deleting`; once it has finished the resource shows its new status and 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 volume, is refused when either has one. A purchased change, such as a resize, is an operation from the moment its Checkout Session is created until the change is applied, the session expires or its order is canceled. Renaming and replacing labels or notes are not operations and are accepted at any time. **Updating.** A `PATCH` carries only mutable fields, all optional and at least one given, and answers 200 when only descriptive fields changed and 202 when an operation started. An operational field (`instance_type_id`, `size_gib`, `bandwidth_mbps`) cannot be combined with any other field in the same request: it is refused with 422 `UPDATE_FIELDS_COMBINED`, because a rename that committed beside a change that was then refused would leave the request half applied.
- * - **Billing relationships.** A purchased resource records its `checkout_session_id` and, once checkout completes, its `order_id`, `order_item_id` and `subscription_id`. Its `access_state` is `pending` until the order is accepted and delivery settles it, then `enabled`; a subscription that lapses suspends or reclaims the resource it pays for. Deleting a resource that subscriptions pay for cancels the subscriptions of its `release_set` in Billing, and the deletion answers with that cancellation.
- * - **Availability zones.** A volume and an instance must reside in the same availability zone to be attached. An instance type and a volume type each belong to one availability zone, as on GCP, so a purchase names the type and the type names the zone; the volumes bought with an instance have to be of types of the instance type's zone.
- * - **IPv6 is routed, not translated.** A virtual private cloud with IPv6 holds a /56 and each of its subnets a /64 of it, as on Alibaba Cloud, Tencent Cloud and Azure; IPv6 and its security groups require no EIP or NAT gateway. EIP and NATGateway are IPv4 products; IPv6 EIP, NAT66 and IPv6 port forwarding are not supported.
- * - **Elastic IP release.** A released address returns to available inventory as soon as its cleanup is confirmed, with no cooldown period. Removing or replacing an elastic IP's association keeps the address held by the project and does not release it.
- * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
- *
- * ## Resource identifiers
- *
- * Compute resource IDs use the fixed TypeID prefix declared in their schema. UUID text is not accepted for these resource IDs. Project, order, subscription and Billing Plan identifiers remain UUIDs. Historical operation-log subject IDs are audit facts and are not rewritten.
- *
- * ## Error meta
- *
- * Resource identifiers in an error's `meta` (`resource_id`, `volume_id`, `network_interface_id` and the like) are TypeIDs, in the same form as the identifiers in resources. `meta.resource_type` is the resource's name as written in paths, with underscores: `instance`, `volume`, `elastic_ip`, `network_interface`, `virtual_private_cloud`, `private_image`, `volume_backup`, and so on.
- * OpenAPI spec version: 2.0.0
- */
-import * as zod from "zod";
-export const ElasticIPAssociationIDMin = 41;
-export const ElasticIPAssociationIDMax = 41;
-export const ElasticIPAssociationIDRegExp = new RegExp("^eipassociation_[0-7][0123456789abcdefghjkmnpqrstvwxyz]{25}$");
-export const ElasticIPAssociationID = zod
-    .string()
-    .min(ElasticIPAssociationIDMin)
-    .max(ElasticIPAssociationIDMax)
-    .regex(ElasticIPAssociationIDRegExp)
-    .describe("Compute ElasticIPAssociation TypeID. UUID text is not accepted.");

package/dist/compute/v2/generated/validators/elasticIPLineID.zod.js

@@ -1,44 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Compute API
- * Leaflow Compute user API for managing instances, volumes, snapshots, volume backups, public and private images, virtual private clouds, subnets, routes, security groups, network interfaces and elastic IPs.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `scopedTokenAuth` security scheme. The catalog reads, which list and retrieve regions, availability zones, instance types, volume types, public images and elastic IP lines, also answer without a token, so a visitor can configure a purchase and price it with Billing before signing in. A token given to them is still verified, and an invalid one is refused.
- *
- * ## Conventions
- *
- * - **Purchases.** A purchase that creates resources returns them together with the `checkout_session_id` of its Billing Checkout Session and, once checkout completes, its `order_id`. They are readable at once and start as `pending`: checkout may not be complete, 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, the resource is created: it stays `pending`, then reaches its usual status, such as `running` or `available`. When the Checkout Session expires, 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. A purchased change, such as a resize requested with `instance_type_id`, `size_gib` or `bandwidth_mbps` on the resource, returns the resource unchanged with the Checkout Session for the change, and applies once its order is accepted.
- * - **Commercial terms.** Compute catalogs describe technical specifications and, for each order line a purchase makes, how it is sold in Billing (a `BillingComponent`: its Plan, dimensions, what its quantity counts and what its meters read); prices, amounts and currency belong to Billing. A purchase chooses its terms with `billing`, and Billing selects the matching price. Read prices and their rates with Billing's `search-prices` from those components, quote a proposed purchase with `get-quote`, and a change of a resource by its `subscription_id`; Compute has no quote or price proxy endpoint and returns no amounts.
- * - **Checkout.** `checkout` is passed to Billing unchanged. Omit it for automatic checkout, which completes checkout within the request and pays from eligible credit grants and balance; 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` with an open Checkout Session and no order, even for a zero total; nothing is created until the customer completes checkout in Billing, where a promotion code can be applied, and the order is paid. Do not submit the purchase again after paying; after an uncertain response, look the Checkout Session up in Billing first.
- * - **Quotas.** A creation, purchase or resize that adds to what a project holds in a region is checked against the project's quota there before anything is ordered or created, and is refused with HTTP 409 `COMPUTE_PROJECT_QUOTA_EXCEEDED`, whose `meta` names the `resource`, its `limit`, the amount `used` and the amount `requested`. An instance purchase counts the volumes, the new primary network interface and the new elastic IP bought with each instance. Read the limits with `list-quotas`; a limit no operator set is the platform default.
- * - **Projects.** Resource ownership and project identifiers refer to IAM platform projects, not OpenStack tenants. Instances, images and networks share one infrastructure OpenStack project; the platform project remains the authorization and ownership boundary.
- * - **Custom methods.** An action that is not one of the standard methods (list, get, create, update, delete) is a custom method, `POST` on the resource's path followed by `:` and the verb, as in `POST /api/v2/instances/{id}:reboot` (AIP-136). A state is changed by its custom method, never by writing the state: `:start` and `:stop`, `:rescue` and `:unrescue`, `:associate` and `:disassociate`.
- * - **Operations.** Requests such as `:start`, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `status` names it, as in `starting` or `deleting`; once it has finished the resource shows its new status and 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 volume, is refused when either has one. A purchased change, such as a resize, is an operation from the moment its Checkout Session is created until the change is applied, the session expires or its order is canceled. Renaming and replacing labels or notes are not operations and are accepted at any time. **Updating.** A `PATCH` carries only mutable fields, all optional and at least one given, and answers 200 when only descriptive fields changed and 202 when an operation started. An operational field (`instance_type_id`, `size_gib`, `bandwidth_mbps`) cannot be combined with any other field in the same request: it is refused with 422 `UPDATE_FIELDS_COMBINED`, because a rename that committed beside a change that was then refused would leave the request half applied.
- * - **Billing relationships.** A purchased resource records its `checkout_session_id` and, once checkout completes, its `order_id`, `order_item_id` and `subscription_id`. Its `access_state` is `pending` until the order is accepted and delivery settles it, then `enabled`; a subscription that lapses suspends or reclaims the resource it pays for. Deleting a resource that subscriptions pay for cancels the subscriptions of its `release_set` in Billing, and the deletion answers with that cancellation.
- * - **Availability zones.** A volume and an instance must reside in the same availability zone to be attached. An instance type and a volume type each belong to one availability zone, as on GCP, so a purchase names the type and the type names the zone; the volumes bought with an instance have to be of types of the instance type's zone.
- * - **IPv6 is routed, not translated.** A virtual private cloud with IPv6 holds a /56 and each of its subnets a /64 of it, as on Alibaba Cloud, Tencent Cloud and Azure; IPv6 and its security groups require no EIP or NAT gateway. EIP and NATGateway are IPv4 products; IPv6 EIP, NAT66 and IPv6 port forwarding are not supported.
- * - **Elastic IP release.** A released address returns to available inventory as soon as its cleanup is confirmed, with no cooldown period. Removing or replacing an elastic IP's association keeps the address held by the project and does not release it.
- * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
- *
- * ## Resource identifiers
- *
- * Compute resource IDs use the fixed TypeID prefix declared in their schema. UUID text is not accepted for these resource IDs. Project, order, subscription and Billing Plan identifiers remain UUIDs. Historical operation-log subject IDs are audit facts and are not rewritten.
- *
- * ## Error meta
- *
- * Resource identifiers in an error's `meta` (`resource_id`, `volume_id`, `network_interface_id` and the like) are TypeIDs, in the same form as the identifiers in resources. `meta.resource_type` is the resource's name as written in paths, with underscores: `instance`, `volume`, `elastic_ip`, `network_interface`, `virtual_private_cloud`, `private_image`, `volume_backup`, and so on.
- * OpenAPI spec version: 2.0.0
- */
-import * as zod from "zod";
-export const ElasticIPLineIDMin = 34;
-export const ElasticIPLineIDMax = 34;
-export const ElasticIPLineIDRegExp = new RegExp("^eipline_[0-7][0123456789abcdefghjkmnpqrstvwxyz]{25}$");
-export const ElasticIPLineID = zod
-    .string()
-    .min(ElasticIPLineIDMin)
-    .max(ElasticIPLineIDMax)
-    .regex(ElasticIPLineIDRegExp)
-    .describe("Compute ElasticIPLine TypeID. UUID text is not accepted.");

package/dist/compute/v2/generated/validators/iPv4HostAddress.zod.d.ts

@@ -1,41 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Compute API
- * Leaflow Compute user API for managing instances, volumes, snapshots, volume backups, public and private images, virtual private clouds, subnets, routes, security groups, network interfaces and elastic IPs.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `scopedTokenAuth` security scheme. The catalog reads, which list and retrieve regions, availability zones, instance types, volume types, public images and elastic IP lines, also answer without a token, so a visitor can configure a purchase and price it with Billing before signing in. A token given to them is still verified, and an invalid one is refused.
- *
- * ## Conventions
- *
- * - **Purchases.** A purchase that creates resources returns them together with the `checkout_session_id` of its Billing Checkout Session and, once checkout completes, its `order_id`. They are readable at once and start as `pending`: checkout may not be complete, 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, the resource is created: it stays `pending`, then reaches its usual status, such as `running` or `available`. When the Checkout Session expires, 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. A purchased change, such as a resize requested with `instance_type_id`, `size_gib` or `bandwidth_mbps` on the resource, returns the resource unchanged with the Checkout Session for the change, and applies once its order is accepted.
- * - **Commercial terms.** Compute catalogs describe technical specifications and, for each order line a purchase makes, how it is sold in Billing (a `BillingComponent`: its Plan, dimensions, what its quantity counts and what its meters read); prices, amounts and currency belong to Billing. A purchase chooses its terms with `billing`, and Billing selects the matching price. Read prices and their rates with Billing's `search-prices` from those components, quote a proposed purchase with `get-quote`, and a change of a resource by its `subscription_id`; Compute has no quote or price proxy endpoint and returns no amounts.
- * - **Checkout.** `checkout` is passed to Billing unchanged. Omit it for automatic checkout, which completes checkout within the request and pays from eligible credit grants and balance; 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` with an open Checkout Session and no order, even for a zero total; nothing is created until the customer completes checkout in Billing, where a promotion code can be applied, and the order is paid. Do not submit the purchase again after paying; after an uncertain response, look the Checkout Session up in Billing first.
- * - **Quotas.** A creation, purchase or resize that adds to what a project holds in a region is checked against the project's quota there before anything is ordered or created, and is refused with HTTP 409 `COMPUTE_PROJECT_QUOTA_EXCEEDED`, whose `meta` names the `resource`, its `limit`, the amount `used` and the amount `requested`. An instance purchase counts the volumes, the new primary network interface and the new elastic IP bought with each instance. Read the limits with `list-quotas`; a limit no operator set is the platform default.
- * - **Projects.** Resource ownership and project identifiers refer to IAM platform projects, not OpenStack tenants. Instances, images and networks share one infrastructure OpenStack project; the platform project remains the authorization and ownership boundary.
- * - **Custom methods.** An action that is not one of the standard methods (list, get, create, update, delete) is a custom method, `POST` on the resource's path followed by `:` and the verb, as in `POST /api/v2/instances/{id}:reboot` (AIP-136). A state is changed by its custom method, never by writing the state: `:start` and `:stop`, `:rescue` and `:unrescue`, `:associate` and `:disassociate`.
- * - **Operations.** Requests such as `:start`, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `status` names it, as in `starting` or `deleting`; once it has finished the resource shows its new status and 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 volume, is refused when either has one. A purchased change, such as a resize, is an operation from the moment its Checkout Session is created until the change is applied, the session expires or its order is canceled. Renaming and replacing labels or notes are not operations and are accepted at any time. **Updating.** A `PATCH` carries only mutable fields, all optional and at least one given, and answers 200 when only descriptive fields changed and 202 when an operation started. An operational field (`instance_type_id`, `size_gib`, `bandwidth_mbps`) cannot be combined with any other field in the same request: it is refused with 422 `UPDATE_FIELDS_COMBINED`, because a rename that committed beside a change that was then refused would leave the request half applied.
- * - **Billing relationships.** A purchased resource records its `checkout_session_id` and, once checkout completes, its `order_id`, `order_item_id` and `subscription_id`. Its `access_state` is `pending` until the order is accepted and delivery settles it, then `enabled`; a subscription that lapses suspends or reclaims the resource it pays for. Deleting a resource that subscriptions pay for cancels the subscriptions of its `release_set` in Billing, and the deletion answers with that cancellation.
- * - **Availability zones.** A volume and an instance must reside in the same availability zone to be attached. An instance type and a volume type each belong to one availability zone, as on GCP, so a purchase names the type and the type names the zone; the volumes bought with an instance have to be of types of the instance type's zone.
- * - **IPv6 is routed, not translated.** A virtual private cloud with IPv6 holds a /56 and each of its subnets a /64 of it, as on Alibaba Cloud, Tencent Cloud and Azure; IPv6 and its security groups require no EIP or NAT gateway. EIP and NATGateway are IPv4 products; IPv6 EIP, NAT66 and IPv6 port forwarding are not supported.
- * - **Elastic IP release.** A released address returns to available inventory as soon as its cleanup is confirmed, with no cooldown period. Removing or replacing an elastic IP's association keeps the address held by the project and does not release it.
- * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
- *
- * ## Resource identifiers
- *
- * Compute resource IDs use the fixed TypeID prefix declared in their schema. UUID text is not accepted for these resource IDs. Project, order, subscription and Billing Plan identifiers remain UUIDs. Historical operation-log subject IDs are audit facts and are not rewritten.
- *
- * ## Error meta
- *
- * Resource identifiers in an error's `meta` (`resource_id`, `volume_id`, `network_interface_id` and the like) are TypeIDs, in the same form as the identifiers in resources. `meta.resource_type` is the resource's name as written in paths, with underscores: `instance`, `volume`, `elastic_ip`, `network_interface`, `virtual_private_cloud`, `private_image`, `volume_backup`, and so on.
- * OpenAPI spec version: 2.0.0
- */
-import * as zod from "zod";
-export declare const IPv4HostAddressMin = 7;
-export declare const IPv4HostAddressMax = 15;
-export declare const IPv4HostAddressRegExp: RegExp;
-export declare const IPv4HostAddress: zod.ZodString;
-export type IPv4HostAddress = zod.input<typeof IPv4HostAddress>;
-export type IPv4HostAddressOutput = zod.output<typeof IPv4HostAddress>;