@leaflow/sdk 0.0.0-dev.53.gd8db059 → 0.0.0-dev.538.g0285c19

package/dist/dns/v1/generated/validators/modifyRecordSetRequestBody.zod.js

@@ -0,0 +1,80 @@
+/**
+ * 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 * as zod from "zod";
+export const modifyRecordSetRequestBodyAddItemMax = 4096;
+export const modifyRecordSetRequestBodyAddMax = 100;
+export const modifyRecordSetRequestBodyRemoveItemMax = 4096;
+export const modifyRecordSetRequestBodyRemoveMax = 100;
+export const modifyRecordSetRequestBodyTtlDefault = 300;
+export const modifyRecordSetRequestBodyTtlMin = 0;
+export const modifyRecordSetRequestBodyTtlMax = 604800;
+export const ModifyRecordSetRequestBody = zod
+    .strictObject({
+    add: zod
+        .array(zod.string().min(1).max(modifyRecordSetRequestBodyAddItemMax))
+        .min(1)
+        .max(modifyRecordSetRequestBodyAddMax)
+        .optional()
+        .describe("The values to add. Values already present are rejected by the provider. Syntax as described on RecordSetResource.values"),
+    remove: zod
+        .array(zod.string().min(1).max(modifyRecordSetRequestBodyRemoveItemMax))
+        .min(1)
+        .max(modifyRecordSetRequestBodyRemoveMax)
+        .optional()
+        .describe("The values to remove. Values that are not present are skipped. Syntax as described on RecordSetResource.values"),
+    ttl: zod
+        .int()
+        .min(modifyRecordSetRequestBodyTtlMin)
+        .max(modifyRecordSetRequestBodyTtlMax)
+        .default(modifyRecordSetRequestBodyTtlDefault)
+        .describe("Time to live, in seconds, applied to the values in `add`. 0 leaves the choice to the provider. The time to live of values already in the set is not changed; use `PUT` for that"),
+})
+    .describe("Names the values to add and to remove. Anything not named is left in place. At least one of `add` and `remove` is required, and no value may appear in both.");

package/dist/dns/v1/generated/validators/offsetPagination.zod.d.ts

@@ -0,0 +1,59 @@
+/**
+ * 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 * as zod from "zod";
+export declare const offsetPaginationTotalCountMin = 0;
+export declare const OffsetPagination: zod.ZodObject<{
+    page: zod.ZodInt;
+    page_size: zod.ZodInt;
+    total_count: zod.ZodOptional<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type OffsetPagination = zod.input<typeof OffsetPagination>;
+export type OffsetPaginationOutput = zod.output<typeof OffsetPagination>;

package/dist/dns/v1/generated/validators/offsetPagination.zod.js

@@ -0,0 +1,59 @@
+/**
+ * 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 * as zod from "zod";
+export const offsetPaginationTotalCountMin = 0;
+export const OffsetPagination = zod
+    .strictObject({
+    page: zod.int().min(1),
+    page_size: zod.int().min(1),
+    total_count: zod.int().min(offsetPaginationTotalCountMin).optional(),
+})
+    .describe("Pagination metadata for stable numbered pages. total_count is returned only when the operation can determine it without an unbounded scan.");

package/dist/dns/v1/generated/validators/provider.zod.d.ts

@@ -0,0 +1,59 @@
+/**
+ * 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 * as zod from "zod";
+export declare const Provider: zod.ZodEnum<{
+    cloudflare: "cloudflare";
+    tencentcloud: "tencentcloud";
+    alidns: "alidns";
+    route53: "route53";
+}>;
+export type Provider = zod.input<typeof Provider>;
+export type ProviderOutput = zod.output<typeof Provider>;

package/dist/dns/v1/generated/validators/provider.zod.js

@@ -0,0 +1,54 @@
+/**
+ * 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 * as zod from "zod";
+export const Provider = zod
+    .enum(["cloudflare", "tencentcloud", "alidns", "route53"])
+    .describe("A supported DNS provider.");

package/dist/dns/v1/generated/validators/recordSetResource.zod.d.ts

@@ -0,0 +1,69 @@
+/**
+ * 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 * as zod from "zod";
+export declare const RecordSetResource: zod.ZodObject<{
+    name: zod.ZodString;
+    ttl: zod.ZodInt;
+    type: zod.ZodEnum<{
+        A: "A";
+        AAAA: "AAAA";
+        CNAME: "CNAME";
+        TXT: "TXT";
+        MX: "MX";
+        NS: "NS";
+        SRV: "SRV";
+        CAA: "CAA";
+    }>;
+    values: zod.ZodArray<zod.ZodString>;
+    zone: zod.ZodString;
+}, zod.z.core.$strict>;
+export type RecordSetResource = zod.input<typeof RecordSetResource>;
+export type RecordSetResourceOutput = zod.output<typeof RecordSetResource>;

package/dist/dns/v1/generated/validators/recordSetResource.zod.js

@@ -0,0 +1,63 @@
+/**
+ * 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 * as zod from "zod";
+import { RecordType } from "./recordType.zod.js";
+export const RecordSetResource = zod
+    .strictObject({
+    name: zod.string().describe("The name relative to the domain. `@` denotes the domain itself"),
+    ttl: zod.int().describe("Time to live, in seconds. 0 leaves the choice to the provider"),
+    type: RecordType,
+    values: zod
+        .array(zod.string())
+        .describe('Every value in this record set, in unescaped zone-file RDATA syntax:\n\n- `A`, `AAAA`: `192.0.2.1`, `2001:db8::1`\n- `CNAME`, `NS`: `target.example.com.`, absolute, with a trailing dot\n- `TXT`: the text itself, neither quoted nor escaped\n- `MX`: `10 mail.example.com.`\n- `SRV`: `10 20 443 target.example.com.`\n- `CAA`: `0 issue "letsencrypt.org"`'),
+    zone: zod.string().describe("The domain in absolute form, with a trailing dot"),
+})
+    .describe("Every record sharing a name and a type.");

package/dist/dns/v1/generated/validators/recordType.zod.d.ts

@@ -0,0 +1,63 @@
+/**
+ * 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 * as zod from "zod";
+export declare const RecordType: zod.ZodEnum<{
+    A: "A";
+    AAAA: "AAAA";
+    CNAME: "CNAME";
+    TXT: "TXT";
+    MX: "MX";
+    NS: "NS";
+    SRV: "SRV";
+    CAA: "CAA";
+}>;
+export type RecordType = zod.input<typeof RecordType>;
+export type RecordTypeOutput = zod.output<typeof RecordType>;

package/dist/dns/v1/generated/validators/recordType.zod.js

@@ -0,0 +1,54 @@
+/**
+ * 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 * as zod from "zod";
+export const RecordType = zod
+    .enum(["A", "AAAA", "CNAME", "TXT", "MX", "NS", "SRV", "CAA"])
+    .describe("A DNS record type.\n\nThe listed types are those this API supports uniformly across every provider. HTTPS and\nSVCB are not yet available.");

package/dist/dns/v1/generated/validators/renameCredentialRequestBody.zod.d.ts

@@ -0,0 +1,57 @@
+/**
+ * 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 * as zod from "zod";
+export declare const renameCredentialRequestBodyNameMax = 128;
+export declare const RenameCredentialRequestBody: zod.ZodObject<{
+    name: zod.ZodString;
+}, zod.z.core.$strict>;
+export type RenameCredentialRequestBody = zod.input<typeof RenameCredentialRequestBody>;
+export type RenameCredentialRequestBodyOutput = zod.output<typeof RenameCredentialRequestBody>;