@leaflow/sdk 0.0.0-dev.42.g9fdf74a → 0.0.0-dev.422.gef294af

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

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

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

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

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

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

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

@@ -0,0 +1,3 @@
+export * from "./generated/functions.js";
+export * from "./generated/models.js";
+export * as schemas from "./generated/schemas.zod.js";

package/dist/compute/v2/index.js

@@ -0,0 +1,3 @@
+export * from "./generated/functions.js";
+export * from "./generated/models.js";
+export * as schemas from "./generated/schemas.zod.js";

package/dist/dns/v1/generated/functions.d.ts

@@ -0,0 +1,393 @@
+/**
+ * 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 { CreateCredentialRequestBody, CredentialResource, DeleteRecordSetParams, Error, LengthAwarePageCredentialResource, LengthAwarePageRecordSetResource, ListCredentialsParams, ListRecordsParams, ListZonesParams, ModifyRecordSetParams, ModifyRecordSetRequestBody, RecordSetResource, RecordType, RenameCredentialRequestBody, SetRecordSetParams, SetRecordSetRequestBody, ZoneListResponseBody } from "./models.js";
+export type HTTPStatusCode1xx = 100 | 101 | 102 | 103;
+export type HTTPStatusCode2xx = 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207;
+export type HTTPStatusCode3xx = 300 | 301 | 302 | 303 | 304 | 305 | 307 | 308;
+export type HTTPStatusCode4xx = 400 | 401 | 402 | 403 | 404 | 405 | 406 | 407 | 408 | 409 | 410 | 411 | 412 | 413 | 414 | 415 | 416 | 417 | 418 | 419 | 420 | 421 | 422 | 423 | 424 | 426 | 428 | 429 | 431 | 451;
+export type HTTPStatusCode5xx = 500 | 501 | 502 | 503 | 504 | 505 | 507 | 511;
+export type HTTPStatusCodes = HTTPStatusCode1xx | HTTPStatusCode2xx | HTTPStatusCode3xx | HTTPStatusCode4xx | HTTPStatusCode5xx;
+export type listCredentialsResponse200 = {
+    data: LengthAwarePageCredentialResource;
+    status: 200;
+};
+export type listCredentialsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type listCredentialsResponseSuccess = listCredentialsResponse200 & {
+    headers: Headers;
+};
+export type listCredentialsResponseError = listCredentialsResponseDefault & {
+    headers: Headers;
+};
+export type listCredentialsResponse = listCredentialsResponseSuccess | listCredentialsResponseError;
+export declare const getListCredentialsUrl: (params?: ListCredentialsParams) => string;
+/**
+ * @summary List provider credentials
+ */
+export declare const listCredentials: (params?: ListCredentialsParams, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<listCredentialsResponse>;
+export type createCredentialResponse201 = {
+    data: CredentialResource;
+    status: 201;
+};
+export type createCredentialResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 201>;
+};
+export type createCredentialResponseSuccess = createCredentialResponse201 & {
+    headers: Headers;
+};
+export type createCredentialResponseError = createCredentialResponseDefault & {
+    headers: Headers;
+};
+export type createCredentialResponse = createCredentialResponseSuccess | createCredentialResponseError;
+export declare const getCreateCredentialUrl: () => string;
+/**
+ * The credential is validated against the provider before it is accepted. A credential that
+ * cannot list domains is rejected with `CREDENTIAL_REJECTED_UPSTREAM` and is not stored.
+ *
+ * `provider` selects which configuration block is required: `provider: cloudflare` requires
+ * the `cloudflare` block, and the remaining blocks are ignored. Omitting the matching block
+ * returns `CREDENTIAL_CONFIG_MISSING`.
+ *
+ * Registering a credential that is already held by this project returns
+ * `CREDENTIAL_DUPLICATE`. Provider rate limits apply per credential, so a second copy grants
+ * no additional capacity.
+ *
+ * The submitted credential material is not returned by this or any other operation.
+ * @summary Register a provider credential
+ */
+export declare const createCredential: (createCredentialRequestBody: CreateCredentialRequestBody, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<createCredentialResponse>;
+export type getCredentialResponse200 = {
+    data: CredentialResource;
+    status: 200;
+};
+export type getCredentialResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getCredentialResponseSuccess = getCredentialResponse200 & {
+    headers: Headers;
+};
+export type getCredentialResponseError = getCredentialResponseDefault & {
+    headers: Headers;
+};
+export type getCredentialResponse = getCredentialResponseSuccess | getCredentialResponseError;
+export declare const getGetCredentialUrl: (credentialId: string) => string;
+/**
+ * @summary Get a provider credential
+ */
+export declare const getCredential: (credentialId: string, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<getCredentialResponse>;
+export type renameCredentialResponse200 = {
+    data: CredentialResource;
+    status: 200;
+};
+export type renameCredentialResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type renameCredentialResponseSuccess = renameCredentialResponse200 & {
+    headers: Headers;
+};
+export type renameCredentialResponseError = renameCredentialResponseDefault & {
+    headers: Headers;
+};
+export type renameCredentialResponse = renameCredentialResponseSuccess | renameCredentialResponseError;
+export declare const getRenameCredentialUrl: (credentialId: string) => string;
+/**
+ * Only the display name can be changed. To use different credential material, delete this
+ * credential and register a new one: a credential's identity does not change over its
+ * lifetime.
+ * @summary Rename a provider credential
+ */
+export declare const renameCredential: (credentialId: string, renameCredentialRequestBody: RenameCredentialRequestBody, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<renameCredentialResponse>;
+export type deleteCredentialResponse204 = {
+    data: void;
+    status: 204;
+};
+export type deleteCredentialResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 204>;
+};
+export type deleteCredentialResponseSuccess = deleteCredentialResponse204 & {
+    headers: Headers;
+};
+export type deleteCredentialResponseError = deleteCredentialResponseDefault & {
+    headers: Headers;
+};
+export type deleteCredentialResponse = deleteCredentialResponseSuccess | deleteCredentialResponseError;
+export declare const getDeleteCredentialUrl: (credentialId: string) => string;
+/**
+ * Domains reachable only through this credential stop appearing in `GET /zones` and can no
+ * longer be read or written through this API.
+ *
+ * **No DNS record is modified.** Deleting a credential withdraws this project's access to the
+ * provider account; it does not remove anything that was published there.
+ * @summary Delete a provider credential
+ */
+export declare const deleteCredential: (credentialId: string, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<deleteCredentialResponse>;
+export type verifyCredentialResponse200 = {
+    data: CredentialResource;
+    status: 200;
+};
+export type verifyCredentialResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type verifyCredentialResponseSuccess = verifyCredentialResponse200 & {
+    headers: Headers;
+};
+export type verifyCredentialResponseError = verifyCredentialResponseDefault & {
+    headers: Headers;
+};
+export type verifyCredentialResponse = verifyCredentialResponseSuccess | verifyCredentialResponseError;
+export declare const getVerifyCredentialUrl: (credentialId: string) => string;
+/**
+ * Checks the credential against the provider and records the outcome in `last_verified_at`
+ * and `last_verify_error`.
+ *
+ * A credential is validated when it is registered. This operation exists for credentials whose
+ * permissions or keys were subsequently changed at the provider, which is a change this API is
+ * not notified of.
+ *
+ * **A failed check returns 200, not an error.** The outcome is reported in
+ * `last_verify_error`: the request itself succeeded, and the answer it obtained is that the
+ * credential is no longer usable.
+ * @summary Re-validate a provider credential
+ */
+export declare const verifyCredential: (credentialId: string, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<verifyCredentialResponse>;
+export type listZonesResponse200 = {
+    data: ZoneListResponseBody;
+    status: 200;
+};
+export type listZonesResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type listZonesResponseSuccess = listZonesResponse200 & {
+    headers: Headers;
+};
+export type listZonesResponseError = listZonesResponseDefault & {
+    headers: Headers;
+};
+export type listZonesResponse = listZonesResponseSuccess | listZonesResponseError;
+export declare const getListZonesUrl: (params?: ListZonesParams) => string;
+/**
+ * Lists every domain reachable through the credentials registered by this project.
+ *
+ * Listings may briefly lag behind domains added or removed at the provider. Set `refresh` for
+ * an up-to-date answer.
+ *
+ * ## A domain that appears more than once
+ *
+ * While a domain is being migrated it commonly exists in both provider accounts at once. Such
+ * a domain is returned once per credential, with the same `zone` and different
+ * `credential_id`.
+ *
+ * `authoritative` reports which entry is the one currently serving queries, determined from
+ * the domain's delegation. `null` means no determination was made: either the domain appears
+ * only once, or its delegation does not identify any of the registered providers — for
+ * example when custom nameservers are in use, or the domain is not delegated at all.
+ *
+ * **Write operations are refused while the determination is `null` and the domain appears more
+ * than once**, with `ZONE_AMBIGUOUS`. Supply `credential_id` on the write request to select a
+ * credential explicitly.
+ * @summary List domains
+ */
+export declare const listZones: (params?: ListZonesParams, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<listZonesResponse>;
+export type listRecordsResponse200 = {
+    data: LengthAwarePageRecordSetResource;
+    status: 200;
+};
+export type listRecordsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type listRecordsResponseSuccess = listRecordsResponse200 & {
+    headers: Headers;
+};
+export type listRecordsResponseError = listRecordsResponseDefault & {
+    headers: Headers;
+};
+export type listRecordsResponse = listRecordsResponseSuccess | listRecordsResponseError;
+export declare const getListRecordsUrl: (zone: string, params?: ListRecordsParams) => string;
+/**
+ * Returns the domain's records grouped into record sets: all records sharing a name and a type
+ * are reported as one entry, with their values in `values`.
+ *
+ * `limit` and `offset` reduce the size of the response but not the time taken to produce it.
+ * For domains with many records, filter by `name` or `type`.
+ * @summary List record sets
+ */
+export declare const listRecords: (zone: string, params?: ListRecordsParams, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<listRecordsResponse>;
+export type getRecordSetResponse200 = {
+    data: RecordSetResource;
+    status: 200;
+};
+export type getRecordSetResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getRecordSetResponseSuccess = getRecordSetResponse200 & {
+    headers: Headers;
+};
+export type getRecordSetResponseError = getRecordSetResponseDefault & {
+    headers: Headers;
+};
+export type getRecordSetResponse = getRecordSetResponseSuccess | getRecordSetResponseError;
+export declare const getGetRecordSetUrl: (zone: string, name: string, type: RecordType) => string;
+/**
+ * Returns `RECORD_SET_NOT_FOUND` when no record of this type exists under this name.
+ * @summary Get a record set
+ */
+export declare const getRecordSet: (zone: string, name: string, type: RecordType, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<getRecordSetResponse>;
+export type setRecordSetResponse200 = {
+    data: RecordSetResource;
+    status: 200;
+};
+export type setRecordSetResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type setRecordSetResponseSuccess = setRecordSetResponse200 & {
+    headers: Headers;
+};
+export type setRecordSetResponseError = setRecordSetResponseDefault & {
+    headers: Headers;
+};
+export type setRecordSetResponse = setRecordSetResponseSuccess | setRecordSetResponseError;
+export declare const getSetRecordSetUrl: (zone: string, name: string, type: RecordType, params?: SetRecordSetParams) => string;
+/**
+ * **This replaces the entire record set.** After this request, the only records under this
+ * name and type are the ones listed in `values`; any value present beforehand and absent here
+ * is removed.
+ *
+ * The record set is created if it does not exist, so this operation both creates and replaces,
+ * and is idempotent.
+ *
+ * Two concurrent requests against the same domain conflict; the second receives `ZONE_BUSY`
+ * and may be retried.
+ *
+ * **Use `PATCH` to add or remove individual values.** Reading the set and submitting a
+ * modified list is a read-modify-write: values added by anything else between those two steps
+ * are stated to be absent, and are therefore removed, with both requests returning 200.
+ * @summary Replace a record set
+ */
+export declare const setRecordSet: (zone: string, name: string, type: RecordType, setRecordSetRequestBody: SetRecordSetRequestBody, params?: SetRecordSetParams, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<setRecordSetResponse>;
+export type modifyRecordSetResponse200 = {
+    data: RecordSetResource;
+    status: 200;
+};
+export type modifyRecordSetResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type modifyRecordSetResponseSuccess = modifyRecordSetResponse200 & {
+    headers: Headers;
+};
+export type modifyRecordSetResponseError = modifyRecordSetResponseDefault & {
+    headers: Headers;
+};
+export type modifyRecordSetResponse = modifyRecordSetResponseSuccess | modifyRecordSetResponseError;
+export declare const getModifyRecordSetUrl: (zone: string, name: string, type: RecordType, params?: ModifyRecordSetParams) => string;
+/**
+ * **Names values to add and remove; anything not named is left in place.** Nothing is read
+ * first, so this is the only operation on a record set safe to issue concurrently. The set is
+ * created if it does not exist.
+ *
+ * Certificate issuance must use this operation for both the challenge record and its cleanup.
+ * `PUT` and `DELETE` state or remove the whole set, so a concurrent issuance's challenge
+ * record is discarded — with every request returning 2xx, and the failure surfacing as the
+ * second certificate failing validation.
+ *
+ * `add` is applied before `remove`, so a request carrying both changes a value without the
+ * name ever resolving without it: the set briefly holds one value too many rather than one too
+ * few. The reverse order, as two requests, leaves a window in which the value is absent — for
+ * a single-valued set, the name does not resolve at all — and an addition that then fails
+ * leaves it gone.
+ *
+ * A value appearing in both `add` and `remove` is rejected rather than resolved in one
+ * direction.
+ *
+ * Values in `remove` that are absent are skipped, so a retried cleanup reaches the same
+ * result. Values in `add` that are already present are rejected by the provider: a record set
+ * cannot hold the same value twice.
+ *
+ * Removing every value leaves an empty set, reported as `values: []`, not `RECORD_SET_NOT_FOUND`.
+ * @summary Add or remove values in a record set
+ */
+export declare const modifyRecordSet: (zone: string, name: string, type: RecordType, modifyRecordSetRequestBody: ModifyRecordSetRequestBody, params?: ModifyRecordSetParams, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<modifyRecordSetResponse>;
+export type deleteRecordSetResponse204 = {
+    data: void;
+    status: 204;
+};
+export type deleteRecordSetResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 204>;
+};
+export type deleteRecordSetResponseSuccess = deleteRecordSetResponse204 & {
+    headers: Headers;
+};
+export type deleteRecordSetResponseError = deleteRecordSetResponseDefault & {
+    headers: Headers;
+};
+export type deleteRecordSetResponse = deleteRecordSetResponseSuccess | deleteRecordSetResponseError;
+export declare const getDeleteRecordSetUrl: (zone: string, name: string, type: RecordType, params?: DeleteRecordSetParams) => string;
+/**
+ * Removes every record under this name and type. **To remove part of a set, use `PATCH`**,
+ * which is safe to issue concurrently; this operation and `PUT` are not.
+ *
+ * Providers reject removal of the last NS record set at the apex of a domain, which would
+ * withdraw the domain from DNS entirely.
+ * @summary Delete a record set
+ */
+export declare const deleteRecordSet: (zone: string, name: string, type: RecordType, params?: DeleteRecordSetParams, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<deleteRecordSetResponse>;