@leaflow/sdk 0.0.0-dev.33.g080e5fd → 0.0.0-dev.330.gb996dfa

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

@@ -0,0 +1,29 @@
+/**
+ * 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 withdrawalPreviewRequestAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const WithdrawalPreviewRequest = zod.strictObject({
+    billing_account_id: zod.int(),
+    amount: zod.string().regex(withdrawalPreviewRequestAmountRegExp).optional(),
+});

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

@@ -0,0 +1,39 @@
+/**
+ * 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 withdrawalSourceAmountRegExp: RegExp;
+export declare const withdrawalSourceCurrencyMin = 3;
+export declare const withdrawalSourceCurrencyMax = 3;
+export declare const withdrawalSourceCardLast4RegExp: RegExp;
+export declare const WithdrawalSource: zod.ZodObject<{
+    amount: zod.ZodString;
+    currency: zod.ZodString;
+    received_at: zod.z.ZodISODateTime;
+    payment_gateway: zod.ZodString;
+    method_type: zod.ZodString;
+    card_brand: zod.ZodOptional<zod.ZodString>;
+    card_last4: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type WithdrawalSource = zod.input<typeof WithdrawalSource>;
+export type WithdrawalSourceOutput = zod.output<typeof WithdrawalSource>;

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

@@ -0,0 +1,39 @@
+/**
+ * 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 withdrawalSourceAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const withdrawalSourceCurrencyMin = 3;
+export const withdrawalSourceCurrencyMax = 3;
+export const withdrawalSourceCardLast4RegExp = new RegExp("^[0-9]{4}$");
+export const WithdrawalSource = zod
+    .strictObject({
+    amount: zod.string().regex(withdrawalSourceAmountRegExp),
+    currency: zod.string().min(withdrawalSourceCurrencyMin).max(withdrawalSourceCurrencyMax),
+    received_at: zod.iso.datetime({ offset: true }),
+    payment_gateway: zod.string(),
+    method_type: zod.string(),
+    card_brand: zod.string().optional(),
+    card_last4: zod.string().regex(withdrawalSourceCardLast4RegExp).optional(),
+})
+    .describe("The original top-up and its refund destination. Card details are included when the original payment method was saved; missing card details do not change the original refund route.");

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

@@ -0,0 +1,38 @@
+/**
+ * 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 ZoneListResponseBody: zod.ZodObject<{
+    items: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        name: zod.ZodString;
+        code: zod.ZodString;
+        id: zod.ZodUUID;
+    }, 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 ZoneListResponseBody = zod.input<typeof ZoneListResponseBody>;
+export type ZoneListResponseBodyOutput = zod.output<typeof ZoneListResponseBody>;

package/dist/compute/v1/generated/validators/zoneListResponseBody.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 { ZoneResource } from "./zoneResource.zod.js";
+export const ZoneListResponseBody = zod.strictObject({
+    items: zod.array(ZoneResource).nullable(),
+    pagination: OffsetPagination,
+});

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

@@ -0,0 +1,31 @@
+/**
+ * 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 ZoneResource: zod.ZodObject<{
+    name: zod.ZodString;
+    code: zod.ZodString;
+    id: zod.ZodUUID;
+}, zod.z.core.$strict>;
+export type ZoneResource = zod.input<typeof ZoneResource>;
+export type ZoneResourceOutput = zod.output<typeof ZoneResource>;

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

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

package/dist/compute/v1/index.d.ts

@@ -1,246 +1,3 @@
-export type { paths, components, operations, webhooks } from "./schema.js";
-import type { operations } from "./schema.js";
-/** `GET /api/v1/backups` 成功时的响应体。 */
-export type ListBackupsResult = operations["list-backups"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/backups` 的查询参数。 */
-export type ListBackupsQuery = operations["list-backups"]["parameters"]["query"];
-/** `POST /api/v1/backups` 成功时的响应体。 */
-export type CreateBackupResult = operations["create-backup"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/backups` 的请求体。 */
-export type CreateBackupBody = NonNullable<operations["create-backup"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/backups/{backupId}` 成功时的响应体。 */
-export type GetBackupResult = operations["get-backup"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/backups/{backupId}` 成功时的响应体。 */
-export type RenameBackupResult = operations["rename-backup"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/backups/{backupId}` 的请求体。 */
-export type RenameBackupBody = NonNullable<operations["rename-backup"]["requestBody"]>["content"]["application/json"];
-/** `POST /api/v1/backups/{backupId}/restore` 成功时的响应体。 */
-export type RestoreBackupResult = operations["restore-backup"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/backups/{backupId}/restore` 的请求体。 */
-export type RestoreBackupBody = NonNullable<operations["restore-backup"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/disk-types` 成功时的响应体。 */
-export type ListDiskTypesResult = operations["list-disk-types"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/disk-types` 的查询参数。 */
-export type ListDiskTypesQuery = operations["list-disk-types"]["parameters"]["query"];
-/** `GET /api/v1/images` 成功时的响应体。 */
-export type ListImagesResult = operations["list-images"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/images` 的查询参数。 */
-export type ListImagesQuery = operations["list-images"]["parameters"]["query"];
-/** `GET /api/v1/instance-types` 成功时的响应体。 */
-export type ListInstanceTypesResult = operations["list-instance-types"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/instance-types` 的查询参数。 */
-export type ListInstanceTypesQuery = operations["list-instance-types"]["parameters"]["query"];
-/** `GET /api/v1/regions` 成功时的响应体。 */
-export type ListRegionsResult = operations["list-regions"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/regions/{regionCode}/availability-zones` 成功时的响应体。 */
-export type ListAvailabilityZonesResult = operations["list-availability-zones"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/disks` 成功时的响应体。 */
-export type ListDisksResult = operations["list-disks"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/disks` 的查询参数。 */
-export type ListDisksQuery = operations["list-disks"]["parameters"]["query"];
-/** `POST /api/v1/disks` 成功时的响应体。 */
-export type CreateDiskResult = operations["create-disk"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/disks` 的请求体。 */
-export type CreateDiskBody = NonNullable<operations["create-disk"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/disks/{diskId}` 成功时的响应体。 */
-export type GetDiskResult = operations["get-disk"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/disks/{diskId}` 成功时的响应体。 */
-export type RenameDiskResult = operations["rename-disk"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/disks/{diskId}` 的请求体。 */
-export type RenameDiskBody = NonNullable<operations["rename-disk"]["requestBody"]>["content"]["application/json"];
-/** `POST /api/v1/disks/{diskId}/resize` 成功时的响应体。 */
-export type ResizeDiskResult = operations["resize-disk"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/disks/{diskId}/resize` 的请求体。 */
-export type ResizeDiskBody = NonNullable<operations["resize-disk"]["requestBody"]>["content"]["application/json"];
-/** `POST /api/v1/disks/{diskId}/revert` 成功时的响应体。 */
-export type RevertDiskResult = operations["revert-disk"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/disks/{diskId}/revert` 的请求体。 */
-export type RevertDiskBody = NonNullable<operations["revert-disk"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/floating-ips` 成功时的响应体。 */
-export type ListFloatingIpsResult = operations["list-floating-ips"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/floating-ips` 成功时的响应体。 */
-export type AllocateFloatingIpResult = operations["allocate-floating-ip"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/floating-ips` 的请求体。 */
-export type AllocateFloatingIpBody = NonNullable<operations["allocate-floating-ip"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/floating-ips/{floatingIpId}` 成功时的响应体。 */
-export type GetFloatingIpResult = operations["get-floating-ip"]["responses"][200]["content"]["application/json"];
-/** `PUT /api/v1/floating-ips/{floatingIpId}/bandwidth` 成功时的响应体。 */
-export type SetFloatingIpBandwidthResult = operations["set-floating-ip-bandwidth"]["responses"][200]["content"]["application/json"];
-/** `PUT /api/v1/floating-ips/{floatingIpId}/bandwidth` 的请求体。 */
-export type SetFloatingIpBandwidthBody = NonNullable<operations["set-floating-ip-bandwidth"]["requestBody"]>["content"]["application/json"];
-/** `DELETE /api/v1/floating-ips/{floatingIpId}/binding` 成功时的响应体。 */
-export type UnbindFloatingIpResult = operations["unbind-floating-ip"]["responses"][200]["content"]["application/json"];
-/** `PUT /api/v1/floating-ips/{floatingIpId}/binding` 成功时的响应体。 */
-export type BindFloatingIpResult = operations["bind-floating-ip"]["responses"][200]["content"]["application/json"];
-/** `PUT /api/v1/floating-ips/{floatingIpId}/binding` 的请求体。 */
-export type BindFloatingIpBody = NonNullable<operations["bind-floating-ip"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/instances` 成功时的响应体。 */
-export type ListInstancesResult = operations["list-instances"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/instances` 的查询参数。 */
-export type ListInstancesQuery = operations["list-instances"]["parameters"]["query"];
-/** `POST /api/v1/instances` 成功时的响应体。 */
-export type LaunchInstanceResult = operations["launch-instance"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/instances` 的请求体。 */
-export type LaunchInstanceBody = NonNullable<operations["launch-instance"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/instances/{instanceId}` 成功时的响应体。 */
-export type GetInstanceResult = operations["get-instance"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/instances/{instanceId}` 成功时的响应体。 */
-export type RenameInstanceResult = operations["rename-instance"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/instances/{instanceId}` 的请求体。 */
-export type RenameInstanceBody = NonNullable<operations["rename-instance"]["requestBody"]>["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/commands` 成功时的响应体。 */
-export type RunInstanceCommandResult = operations["run-instance-command"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/commands` 的请求体。 */
-export type RunInstanceCommandBody = NonNullable<operations["run-instance-command"]["requestBody"]>["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/console` 成功时的响应体。 */
-export type OpenInstanceConsoleResult = operations["open-instance-console"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/instances/{instanceId}/console-output` 成功时的响应体。 */
-export type GetInstanceConsoleOutputResult = operations["get-instance-console-output"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/instances/{instanceId}/console-output` 的查询参数。 */
-export type GetInstanceConsoleOutputQuery = operations["get-instance-console-output"]["parameters"]["query"];
-/** `PUT /api/v1/instances/{instanceId}/labels` 成功时的响应体。 */
-export type SetInstanceLabelsResult = operations["set-instance-labels"]["responses"][200]["content"]["application/json"];
-/** `PUT /api/v1/instances/{instanceId}/labels` 的请求体。 */
-export type SetInstanceLabelsBody = NonNullable<operations["set-instance-labels"]["requestBody"]>["content"]["application/json"];
-/** `PUT /api/v1/instances/{instanceId}/notes` 成功时的响应体。 */
-export type SetInstanceNotesResult = operations["set-instance-notes"]["responses"][200]["content"]["application/json"];
-/** `PUT /api/v1/instances/{instanceId}/notes` 的请求体。 */
-export type SetInstanceNotesBody = NonNullable<operations["set-instance-notes"]["requestBody"]>["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/password` 成功时的响应体。 */
-export type ResetInstancePasswordResult = operations["reset-instance-password"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/password` 的请求体。 */
-export type ResetInstancePasswordBody = NonNullable<operations["reset-instance-password"]["requestBody"]>["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/reboot` 成功时的响应体。 */
-export type RebootInstanceResult = operations["reboot-instance"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/reboot` 的请求体。 */
-export type RebootInstanceBody = NonNullable<operations["reboot-instance"]["requestBody"]>["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/rebuild` 成功时的响应体。 */
-export type RebuildInstanceResult = operations["rebuild-instance"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/rebuild` 的请求体。 */
-export type RebuildInstanceBody = NonNullable<operations["rebuild-instance"]["requestBody"]>["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/resize` 成功时的响应体。 */
-export type ResizeInstanceResult = operations["resize-instance"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/resize` 的请求体。 */
-export type ResizeInstanceBody = NonNullable<operations["resize-instance"]["requestBody"]>["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/resize/confirm` 成功时的响应体。 */
-export type ConfirmInstanceResizeResult = operations["confirm-instance-resize"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/resize/revert` 成功时的响应体。 */
-export type RevertInstanceResizeResult = operations["revert-instance-resize"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/start` 成功时的响应体。 */
-export type StartInstanceResult = operations["start-instance"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/stop` 成功时的响应体。 */
-export type StopInstanceResult = operations["stop-instance"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/instances/{instanceId}/disks` 成功时的响应体。 */
-export type ListInstanceDisksResult = operations["list-instance-disks"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/disks` 成功时的响应体。 */
-export type AttachDiskResult = operations["attach-disk"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/disks` 的请求体。 */
-export type AttachDiskBody = NonNullable<operations["attach-disk"]["requestBody"]>["content"]["application/json"];
-/** `DELETE /api/v1/instances/{instanceId}/disks/{diskId}` 成功时的响应体。 */
-export type DetachDiskResult = operations["detach-disk"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/floating-ips` 成功时的响应体。 */
-export type AttachInstanceFloatingIpResult = operations["attach-instance-floating-ip"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/floating-ips` 的请求体。 */
-export type AttachInstanceFloatingIpBody = NonNullable<operations["attach-instance-floating-ip"]["requestBody"]>["content"]["application/json"];
-/** `DELETE /api/v1/instances/{instanceId}/floating-ips/{floatingIpId}` 成功时的响应体。 */
-export type DetachInstanceFloatingIpResult = operations["detach-instance-floating-ip"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/instances/{instanceId}/ports` 成功时的响应体。 */
-export type ListInstancePortsResult = operations["list-instance-ports"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/ports` 成功时的响应体。 */
-export type AttachPortResult = operations["attach-port"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/instances/{instanceId}/ports` 的请求体。 */
-export type AttachPortBody = NonNullable<operations["attach-port"]["requestBody"]>["content"]["application/json"];
-/** `DELETE /api/v1/instances/{instanceId}/ports/{portId}` 成功时的响应体。 */
-export type DetachPortResult = operations["detach-port"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/operation-logs` 成功时的响应体。 */
-export type ListOperationLogsResult = operations["list-operation-logs"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/operation-logs` 的查询参数。 */
-export type ListOperationLogsQuery = operations["list-operation-logs"]["parameters"]["query"];
-/** `GET /api/v1/ports` 成功时的响应体。 */
-export type ListPortsResult = operations["list-ports"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/ports` 成功时的响应体。 */
-export type CreatePortResult = operations["create-port"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/ports` 的请求体。 */
-export type CreatePortBody = NonNullable<operations["create-port"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/private-images` 成功时的响应体。 */
-export type ListPrivateImagesResult = operations["list-private-images"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/private-images` 的查询参数。 */
-export type ListPrivateImagesQuery = operations["list-private-images"]["parameters"]["query"];
-/** `POST /api/v1/private-images` 成功时的响应体。 */
-export type CreatePrivateImageResult = operations["create-private-image"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/private-images` 的请求体。 */
-export type CreatePrivateImageBody = NonNullable<operations["create-private-image"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/private-images/{privateImageId}` 成功时的响应体。 */
-export type GetPrivateImageResult = operations["get-private-image"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/private-images/{privateImageId}` 成功时的响应体。 */
-export type RenamePrivateImageResult = operations["rename-private-image"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/private-images/{privateImageId}` 的请求体。 */
-export type RenamePrivateImageBody = NonNullable<operations["rename-private-image"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/private-networks` 成功时的响应体。 */
-export type ListPrivateNetworksResult = operations["list-private-networks"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/private-networks` 的查询参数。 */
-export type ListPrivateNetworksQuery = operations["list-private-networks"]["parameters"]["query"];
-/** `POST /api/v1/private-networks` 成功时的响应体。 */
-export type CreatePrivateNetworkResult = operations["create-private-network"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/private-networks` 的请求体。 */
-export type CreatePrivateNetworkBody = NonNullable<operations["create-private-network"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/private-networks/{privateNetworkId}` 成功时的响应体。 */
-export type GetPrivateNetworkResult = operations["get-private-network"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/private-networks/{privateNetworkId}` 成功时的响应体。 */
-export type RenamePrivateNetworkResult = operations["rename-private-network"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/private-networks/{privateNetworkId}` 的请求体。 */
-export type RenamePrivateNetworkBody = NonNullable<operations["rename-private-network"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/private-networks/{privateNetworkId}/ipv6` 成功时的响应体。 */
-export type GetPrivateNetworkIpv6Result = operations["get-private-network-ipv6"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/private-networks/{privateNetworkId}/ipv6` 成功时的响应体。 */
-export type EnablePrivateNetworkIpv6Result = operations["enable-private-network-ipv6"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/private-networks/{privateNetworkId}/routes` 成功时的响应体。 */
-export type ListRoutesResult = operations["list-routes"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/private-networks/{privateNetworkId}/routes` 成功时的响应体。 */
-export type CreateRouteResult = operations["create-route"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/private-networks/{privateNetworkId}/routes` 的请求体。 */
-export type CreateRouteBody = NonNullable<operations["create-route"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/private-networks/{privateNetworkId}/subnets` 成功时的响应体。 */
-export type ListSubnetsResult = operations["list-subnets"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/private-networks/{privateNetworkId}/subnets` 成功时的响应体。 */
-export type CreateSubnetResult = operations["create-subnet"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/private-networks/{privateNetworkId}/subnets` 的请求体。 */
-export type CreateSubnetBody = NonNullable<operations["create-subnet"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/private-networks/{privateNetworkId}/subnets/next-free-cidr` 成功时的响应体。 */
-export type SuggestSubnetCidrResult = operations["suggest-subnet-cidr"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/private-networks/{privateNetworkId}/subnets/next-free-cidr` 的查询参数。 */
-export type SuggestSubnetCidrQuery = operations["suggest-subnet-cidr"]["parameters"]["query"];
-/** `GET /api/v1/security-groups` 成功时的响应体。 */
-export type ListSecurityGroupsResult = operations["list-security-groups"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/security-groups` 的查询参数。 */
-export type ListSecurityGroupsQuery = operations["list-security-groups"]["parameters"]["query"];
-/** `POST /api/v1/security-groups` 成功时的响应体。 */
-export type CreateSecurityGroupResult = operations["create-security-group"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/security-groups` 的请求体。 */
-export type CreateSecurityGroupBody = NonNullable<operations["create-security-group"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/security-groups/{securityGroupId}` 成功时的响应体。 */
-export type GetSecurityGroupResult = operations["get-security-group"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/security-groups/{securityGroupId}` 成功时的响应体。 */
-export type RenameSecurityGroupResult = operations["rename-security-group"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/security-groups/{securityGroupId}` 的请求体。 */
-export type RenameSecurityGroupBody = NonNullable<operations["rename-security-group"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/security-groups/{securityGroupId}/rules` 成功时的响应体。 */
-export type ListSecurityGroupRulesResult = operations["list-security-group-rules"]["responses"][200]["content"]["application/json"];
-/** `POST /api/v1/security-groups/{securityGroupId}/rules` 成功时的响应体。 */
-export type CreateSecurityGroupRuleResult = operations["create-security-group-rule"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/security-groups/{securityGroupId}/rules` 的请求体。 */
-export type CreateSecurityGroupRuleBody = NonNullable<operations["create-security-group-rule"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/snapshots` 成功时的响应体。 */
-export type ListSnapshotsResult = operations["list-snapshots"]["responses"][200]["content"]["application/json"];
-/** `GET /api/v1/snapshots` 的查询参数。 */
-export type ListSnapshotsQuery = operations["list-snapshots"]["parameters"]["query"];
-/** `POST /api/v1/snapshots` 成功时的响应体。 */
-export type CreateSnapshotResult = operations["create-snapshot"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/snapshots` 的请求体。 */
-export type CreateSnapshotBody = NonNullable<operations["create-snapshot"]["requestBody"]>["content"]["application/json"];
-/** `GET /api/v1/snapshots/{snapshotId}` 成功时的响应体。 */
-export type GetSnapshotResult = operations["get-snapshot"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/snapshots/{snapshotId}` 成功时的响应体。 */
-export type RenameSnapshotResult = operations["rename-snapshot"]["responses"][200]["content"]["application/json"];
-/** `PATCH /api/v1/snapshots/{snapshotId}` 的请求体。 */
-export type RenameSnapshotBody = NonNullable<operations["rename-snapshot"]["requestBody"]>["content"]["application/json"];
+export * from "./generated/functions.js";
+export * from "./generated/models.js";
+export * as schemas from "./generated/schemas.zod.js";

package/dist/compute/v1/index.js

@@ -1,5 +1,3 @@
-// 由 scripts/generate-ts.mjs 生成，不要手改。
-//
-// 别名把 operations[...] 那串下标换成一个名字。原始的 paths / components / operations 也
-// 一并导出：paths 是给 openapi-fetch 的 createClient<paths>() 用的。
-export {};
+export * from "./generated/functions.js";
+export * from "./generated/models.js";
+export * as schemas from "./generated/schemas.zod.js";