@leaflow/sdk 0.108.0 → 0.109.0

package/dist/compute/v1/generated/models/suggestSubnetCidrParams.js

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

package/dist/compute/v1/generated/models/terminationPolicy.d.ts

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

package/dist/compute/v1/generated/models/terminationPolicy.js

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

package/dist/compute/v1/generated/models/zoneListResponseBody.d.ts

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

package/dist/compute/v1/generated/models/zoneListResponseBody.js

@@ -1 +0,0 @@
-export {};

package/dist/compute/v1/generated/models/zoneResource.d.ts

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

package/dist/compute/v1/generated/models/zoneResource.js

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

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

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

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

@@ -1,59 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Compute API
- * Leaflow Compute user API for managing instances, disks, snapshots, backups, images, private networks, subnets, routes, security groups, network interfaces and floating IPs.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `scopedTokenAuth` security scheme.
- *
- * ## Conventions
- *
- * - **Purchases.** A purchase that creates resources returns them together with a PlacedOrder. They are readable at once and start as `pending`: the order has not been accepted, nothing exists in the cloud, no inventory such as an address is held, and fields known only after allocation, such as addresses, are null. Once Billing accepts the order, a resource becomes `provisioning` and then reaches its usual status, such as `active` or `available`. When the order is declined, canceled or expires, or creation fails, the resource ends `failed` and `failure_reason` states why; the charge for a resource that failed after acceptance is refunded. Read the order in Billing for checkout and payment progress.
- * - **Pricing.** Catalog items, such as instance types, disk types and public IP pools, carry `pricing`: the prepaid and postpaid options Billing offers for them, in the currency of the project's current billing account, or null when the project has no billing account. They are list amounts before promotion codes, not a checkout guarantee. A purchase chooses one option with `billing`, which applies to all of its components. Every purchase and change has a quote operation beside it, at the same path followed by `/quote`, which returns what checkout would collect without ordering anything.
- * - **Checkout.** Omit `checkout` for automatic checkout, which pays from eligible credit grants and balance when the order is placed; insufficient funds refuse the request with HTTP 422 `BILLING_INSUFFICIENT_FUNDS`, and nothing is created. With `checkout.mode` set to `deferred`, the resources are returned `pending` and nothing is created until checkout is confirmed and paid through Billing. An order whose total is zero, such as a postpaid purchase with nothing due now, completes checkout at placement in either mode and proceeds to provisioning.
- * - **Operations.** Requests such as starting, stopping, attaching or deleting return HTTP 202 with the resource as it is when the request is accepted. While an operation runs, the resource's `operation` field names it; the field is null once the operation has finished, and the resource then shows the result. A resource with an operation in progress refuses another operation with HTTP 409 `COMPUTE_RESOURCE_BUSY`; an operation involving two resources, such as attaching a disk, is refused when either has one. A purchased change, such as a resize, is an operation from the moment its order is placed until it is applied or its order is canceled, including while it awaits checkout. Renaming and replacing labels or notes are not operations and are accepted at any time.
- * - **Billing relationships.** A purchased resource records its `order_id`, `order_item_id` and `subscription_id`. The subscription is `pending` until the order is accepted, `provisioning` while the resource is created, and `active` once it is delivered. Bandwidth is a property of its floating IP, not a separate resource. Snapshots use a purchased per-region count quota, and backups are metered on the region's backup service; neither has an order or subscription of its own.
- * - **Availability zones.** A disk and an instance must reside in the same availability zone to be attached. Instance types and disk types are each bound to one availability zone, so choosing a type determines the zone.
- * - **IPv6 is not sold separately.** Once enabled on a private network, IPv6 addresses are assigned to the instances in that network automatically; they can be neither requested nor released individually.
- * - **Floating IPs have a cooldown period.** A released address is neither available for re-allocation nor handed to another user for some time, so that DNS records and allow-lists still pointing at it do not break immediately.
- * - **Passwords are returned once.** A password generated by the platform during creation or rebuild appears only in that response. Store it immediately.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-import { Money } from "./money.zod.js";
-export const QuotedLine = zod
-    .strictObject({
-    priced: zod
-        .boolean()
-        .describe("Whether the line can be priced. When false, unpriced_reason states what is missing."),
-    unpriced_reason: zod
-        .enum(["none", "no_price"])
-        .describe("Why no price was found; `none` while `priced` is true."),
-    plan_name: zod.string(),
-    unit_amount: zod
-        .union([Money, zod.null()])
-        .describe("Unit price before discounts, with tax included only where the price includes it."),
-    quantity: zod.string().describe("The quantity priced."),
-    amount: zod
-        .union([Money, zod.null()])
-        .describe("Before discounts, including any setup charges. Contains tax only where the price includes it.\nZero for a priced order item with no immediate charge."),
-    discount_amount: zod
-        .union([Money, zod.null()])
-        .describe("Total reduction on this line, including any committed recurring discount."),
-    tax_amount: zod
-        .union([Money, zod.null()])
-        .describe("Tax on the discounted amount, including any tax already contained in that amount."),
-    tax_included_amount: zod
-        .union([Money, zod.null()])
-        .describe("The part of tax_amount already contained in amount minus discount_amount."),
-    total: zod
-        .union([Money, zod.null()])
-        .describe("amount minus discount_amount plus tax_amount minus tax_included_amount."),
-    estimated_usage_amount: zod
-        .union([Money, zod.null()])
-        .describe("Projected charge for this line's future usage over the period stated by the quoting operation,\nat current rates, before discounts and tax and not rounded. Not part of amount or total and\nnot collected at checkout. Null when the line is not billed for usage or its usage cannot be\npriced."),
-    currency: zod.string(),
-})
-    .describe("One calculated purchase line. Fixed purchase amounts are rounded as checkout rounds them.\nWhen priced is false, every monetary field is null. A priced line without an\nimmediate charge has zero amounts; an unavailable unit price remains null.");

package/dist/dns/v1/generated/models/aliDNSConfig.d.ts

@@ -1,70 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow DNS API
- * Manage DNS records across supported providers through a single API. Register a provider
- * credential, and every domain that credential can reach becomes readable and writable here.
- *
- * Reads and writes always reflect the current state at the provider. Records changed through the
- * provider's own console, an ACME client, or any other automation are visible here immediately,
- * and changes made here take effect there.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme.
- *
- * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
- * the token.
- *
- * ## Conventions
- *
- * - **Records are addressed as record sets, not as individual records.** All records sharing a
- *   name and a type form one set — for example, three A records pointing at three addresses. This
- *   API exposes no per-record identifier, because provider-assigned identifiers are neither
- *   portable across providers nor guaranteed to be stable within one.
- * - **`PUT` replaces an entire record set; `PATCH` names individual values.** See below; this is
- *   the single most consequential distinction in this API.
- * - **Confirm which credential owns a domain before writing to it.** The same domain can exist in
- *   more than one provider account — most commonly while a domain is being migrated and the old
- *   account still holds it — and only one of them is actually serving queries.
- * - **Changes do not take effect everywhere at once.** A write reaches the provider immediately,
- *   but resolvers elsewhere continue serving the previous value until its TTL expires. Allow at
- *   least one TTL before verifying a change by resolving the name.
- * - **Credential material is never returned.** No operation, including the one that registers it,
- *   returns the values that were submitted. A credential that was entered incorrectly must be
- *   deleted and registered again.
- *
- * ## PUT or PATCH
- *
- * `PUT` states what a record set should contain. `PATCH` names values to add or remove and leaves
- * the rest alone. The distinction is concurrency.
- *
- * Changing part of a set with `PUT` means reading it and submitting a modified list. That is a
- * read-modify-write: a value added in between — by a concurrent certificate issuance, by another
- * automation, or from the provider's own console — is absent from the submitted list and is
- * therefore removed. Every request in that sequence returns 2xx.
- *
- * `PATCH` reads nothing. It is the only operation on a record set safe to issue concurrently, and
- * the one certificate issuance must use.
- * OpenAPI spec version: 1.0.0
- */
-/**
- * Alibaba Cloud DNS credentials, created under RAM
- */
-export interface AliDNSConfig {
-    /**
-     * @minLength 1
-     * @maxLength 256
-     */
-    access_key_id: string;
-    /**
-     * @minLength 1
-     * @maxLength 256
-     */
-    access_key_secret: string;
-    /**
-     * Defaults to cn-hangzhou
-     * @maxLength 64
-     */
-    region_id?: string;
-}

package/dist/dns/v1/generated/models/aliDNSConfig.js

@@ -1,51 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow DNS API
- * Manage DNS records across supported providers through a single API. Register a provider
- * credential, and every domain that credential can reach becomes readable and writable here.
- *
- * Reads and writes always reflect the current state at the provider. Records changed through the
- * provider's own console, an ACME client, or any other automation are visible here immediately,
- * and changes made here take effect there.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme.
- *
- * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
- * the token.
- *
- * ## Conventions
- *
- * - **Records are addressed as record sets, not as individual records.** All records sharing a
- *   name and a type form one set — for example, three A records pointing at three addresses. This
- *   API exposes no per-record identifier, because provider-assigned identifiers are neither
- *   portable across providers nor guaranteed to be stable within one.
- * - **`PUT` replaces an entire record set; `PATCH` names individual values.** See below; this is
- *   the single most consequential distinction in this API.
- * - **Confirm which credential owns a domain before writing to it.** The same domain can exist in
- *   more than one provider account — most commonly while a domain is being migrated and the old
- *   account still holds it — and only one of them is actually serving queries.
- * - **Changes do not take effect everywhere at once.** A write reaches the provider immediately,
- *   but resolvers elsewhere continue serving the previous value until its TTL expires. Allow at
- *   least one TTL before verifying a change by resolving the name.
- * - **Credential material is never returned.** No operation, including the one that registers it,
- *   returns the values that were submitted. A credential that was entered incorrectly must be
- *   deleted and registered again.
- *
- * ## PUT or PATCH
- *
- * `PUT` states what a record set should contain. `PATCH` names values to add or remove and leaves
- * the rest alone. The distinction is concurrency.
- *
- * Changing part of a set with `PUT` means reading it and submitting a modified list. That is a
- * read-modify-write: a value added in between — by a concurrent certificate issuance, by another
- * automation, or from the provider's own console — is absent from the submitted list and is
- * therefore removed. Every request in that sequence returns 2xx.
- *
- * `PATCH` reads nothing. It is the only operation on a record set safe to issue concurrently, and
- * the one certificate issuance must use.
- * OpenAPI spec version: 1.0.0
- */
-export {};

package/dist/dns/v1/generated/models/cloudflareConfig.d.ts

@@ -1,66 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow DNS API
- * Manage DNS records across supported providers through a single API. Register a provider
- * credential, and every domain that credential can reach becomes readable and writable here.
- *
- * Reads and writes always reflect the current state at the provider. Records changed through the
- * provider's own console, an ACME client, or any other automation are visible here immediately,
- * and changes made here take effect there.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme.
- *
- * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
- * the token.
- *
- * ## Conventions
- *
- * - **Records are addressed as record sets, not as individual records.** All records sharing a
- *   name and a type form one set — for example, three A records pointing at three addresses. This
- *   API exposes no per-record identifier, because provider-assigned identifiers are neither
- *   portable across providers nor guaranteed to be stable within one.
- * - **`PUT` replaces an entire record set; `PATCH` names individual values.** See below; this is
- *   the single most consequential distinction in this API.
- * - **Confirm which credential owns a domain before writing to it.** The same domain can exist in
- *   more than one provider account — most commonly while a domain is being migrated and the old
- *   account still holds it — and only one of them is actually serving queries.
- * - **Changes do not take effect everywhere at once.** A write reaches the provider immediately,
- *   but resolvers elsewhere continue serving the previous value until its TTL expires. Allow at
- *   least one TTL before verifying a change by resolving the name.
- * - **Credential material is never returned.** No operation, including the one that registers it,
- *   returns the values that were submitted. A credential that was entered incorrectly must be
- *   deleted and registered again.
- *
- * ## PUT or PATCH
- *
- * `PUT` states what a record set should contain. `PATCH` names values to add or remove and leaves
- * the rest alone. The distinction is concurrency.
- *
- * Changing part of a set with `PUT` means reading it and submitting a modified list. That is a
- * read-modify-write: a value added in between — by a concurrent certificate issuance, by another
- * automation, or from the provider's own console — is absent from the submitted list and is
- * therefore removed. Every request in that sequence returns 2xx.
- *
- * `PATCH` reads nothing. It is the only operation on a record set safe to issue concurrently, and
- * the one certificate issuance must use.
- * OpenAPI spec version: 1.0.0
- */
-/**
- * Cloudflare credentials, created under My Profile then API Tokens
- */
-export interface CloudflareConfig {
-    /**
-     * An API token with the Zone.DNS edit permission
-     * @minLength 1
-     * @maxLength 512
-     */
-    api_token: string;
-    /**
-     * Optional, and required only when api_token is scoped to a single zone, in which case it is used to enumerate zones
-     * @maxLength 512
-     */
-    zone_token?: string;
-}

package/dist/dns/v1/generated/models/cloudflareConfig.js

@@ -1,51 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow DNS API
- * Manage DNS records across supported providers through a single API. Register a provider
- * credential, and every domain that credential can reach becomes readable and writable here.
- *
- * Reads and writes always reflect the current state at the provider. Records changed through the
- * provider's own console, an ACME client, or any other automation are visible here immediately,
- * and changes made here take effect there.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme.
- *
- * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
- * the token.
- *
- * ## Conventions
- *
- * - **Records are addressed as record sets, not as individual records.** All records sharing a
- *   name and a type form one set — for example, three A records pointing at three addresses. This
- *   API exposes no per-record identifier, because provider-assigned identifiers are neither
- *   portable across providers nor guaranteed to be stable within one.
- * - **`PUT` replaces an entire record set; `PATCH` names individual values.** See below; this is
- *   the single most consequential distinction in this API.
- * - **Confirm which credential owns a domain before writing to it.** The same domain can exist in
- *   more than one provider account — most commonly while a domain is being migrated and the old
- *   account still holds it — and only one of them is actually serving queries.
- * - **Changes do not take effect everywhere at once.** A write reaches the provider immediately,
- *   but resolvers elsewhere continue serving the previous value until its TTL expires. Allow at
- *   least one TTL before verifying a change by resolving the name.
- * - **Credential material is never returned.** No operation, including the one that registers it,
- *   returns the values that were submitted. A credential that was entered incorrectly must be
- *   deleted and registered again.
- *
- * ## PUT or PATCH
- *
- * `PUT` states what a record set should contain. `PATCH` names values to add or remove and leaves
- * the rest alone. The distinction is concurrency.
- *
- * Changing part of a set with `PUT` means reading it and submitting a modified list. That is a
- * read-modify-write: a value added in between — by a concurrent certificate issuance, by another
- * automation, or from the provider's own console — is absent from the submitted list and is
- * therefore removed. Every request in that sequence returns 2xx.
- *
- * `PATCH` reads nothing. It is the only operation on a record set safe to issue concurrently, and
- * the one certificate issuance must use.
- * OpenAPI spec version: 1.0.0
- */
-export {};

package/dist/dns/v1/generated/models/createCredentialRequestBody.d.ts

@@ -1,71 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow DNS API
- * Manage DNS records across supported providers through a single API. Register a provider
- * credential, and every domain that credential can reach becomes readable and writable here.
- *
- * Reads and writes always reflect the current state at the provider. Records changed through the
- * provider's own console, an ACME client, or any other automation are visible here immediately,
- * and changes made here take effect there.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme.
- *
- * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
- * the token.
- *
- * ## Conventions
- *
- * - **Records are addressed as record sets, not as individual records.** All records sharing a
- *   name and a type form one set — for example, three A records pointing at three addresses. This
- *   API exposes no per-record identifier, because provider-assigned identifiers are neither
- *   portable across providers nor guaranteed to be stable within one.
- * - **`PUT` replaces an entire record set; `PATCH` names individual values.** See below; this is
- *   the single most consequential distinction in this API.
- * - **Confirm which credential owns a domain before writing to it.** The same domain can exist in
- *   more than one provider account — most commonly while a domain is being migrated and the old
- *   account still holds it — and only one of them is actually serving queries.
- * - **Changes do not take effect everywhere at once.** A write reaches the provider immediately,
- *   but resolvers elsewhere continue serving the previous value until its TTL expires. Allow at
- *   least one TTL before verifying a change by resolving the name.
- * - **Credential material is never returned.** No operation, including the one that registers it,
- *   returns the values that were submitted. A credential that was entered incorrectly must be
- *   deleted and registered again.
- *
- * ## PUT or PATCH
- *
- * `PUT` states what a record set should contain. `PATCH` names values to add or remove and leaves
- * the rest alone. The distinction is concurrency.
- *
- * Changing part of a set with `PUT` means reading it and submitting a modified list. That is a
- * read-modify-write: a value added in between — by a concurrent certificate issuance, by another
- * automation, or from the provider's own console — is absent from the submitted list and is
- * therefore removed. Every request in that sequence returns 2xx.
- *
- * `PATCH` reads nothing. It is the only operation on a record set safe to issue concurrently, and
- * the one certificate issuance must use.
- * OpenAPI spec version: 1.0.0
- */
-import type { AliDNSConfig } from "./aliDNSConfig.js";
-import type { CloudflareConfig } from "./cloudflareConfig.js";
-import type { Provider } from "./provider.js";
-import type { Route53Config } from "./route53Config.js";
-import type { TencentCloudConfig } from "./tencentCloudConfig.js";
-/**
- * `provider` selects which configuration block is read. The remaining blocks are ignored.
- */
-export interface CreateCredentialRequestBody {
-    alidns?: AliDNSConfig;
-    cloudflare?: CloudflareConfig;
-    /**
-     * A display name for this credential
-     * @minLength 1
-     * @maxLength 128
-     */
-    name: string;
-    provider: Provider;
-    route53?: Route53Config;
-    tencentcloud?: TencentCloudConfig;
-}

package/dist/dns/v1/generated/models/createCredentialRequestBody.js

@@ -1 +0,0 @@
-export {};