@leaflow/sdk 0.0.0-dev.45.g5125469 → 0.0.0-dev.451.gfd4baf5

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

@@ -0,0 +1,55 @@
+/**
+ * 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 renameCredentialRequestBodyNameMax = 128;
+export const RenameCredentialRequestBody = zod.strictObject({
+    name: zod.string().min(1).max(renameCredentialRequestBodyNameMax),
+});

package/dist/dns/v1/generated/validators/route53Config.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 route53ConfigAccessKeyIdMax = 256;
+export declare const route53ConfigRegionMax = 64;
+export declare const route53ConfigSecretAccessKeyMax = 256;
+export declare const route53ConfigSessionTokenMax = 2048;
+export declare const Route53Config: zod.ZodObject<{
+    access_key_id: zod.ZodString;
+    region: zod.ZodOptional<zod.ZodString>;
+    secret_access_key: zod.ZodString;
+    session_token: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type Route53Config = zod.input<typeof Route53Config>;
+export type Route53ConfigOutput = zod.output<typeof Route53Config>;

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

@@ -0,0 +1,71 @@
+/**
+ * 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 route53ConfigAccessKeyIdMax = 256;
+export const route53ConfigRegionMax = 64;
+export const route53ConfigSecretAccessKeyMax = 256;
+export const route53ConfigSessionTokenMax = 2048;
+export const Route53Config = zod
+    .strictObject({
+    access_key_id: zod.string().min(1).max(route53ConfigAccessKeyIdMax),
+    region: zod
+        .string()
+        .max(route53ConfigRegionMax)
+        .optional()
+        .describe("Defaults to us-east-1. Route 53 is a global service, so this affects request signing only"),
+    secret_access_key: zod.string().min(1).max(route53ConfigSecretAccessKeyMax),
+    session_token: zod
+        .string()
+        .max(route53ConfigSessionTokenMax)
+        .optional()
+        .describe("Optional, and required only for temporary STS credentials. Such credentials expire, after which every operation against this provider fails"),
+})
+    .describe("AWS Route 53 credentials");

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

@@ -0,0 +1,56 @@
+/**
+ * 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 SetRecordSetParams: zod.ZodObject<{
+    credential_id: zod.ZodOptional<zod.ZodUUID>;
+}, zod.z.core.$strict>;
+export type SetRecordSetParams = zod.input<typeof SetRecordSetParams>;
+export type SetRecordSetParamsOutput = zod.output<typeof SetRecordSetParams>;

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

@@ -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 const SetRecordSetParams = zod.strictObject({
+    credential_id: zod
+        .uuid()
+        .optional()
+        .describe("Which credential to use. When omitted, the credential is determined from the domain; see ZONE_AMBIGUOUS"),
+});

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

@@ -0,0 +1,62 @@
+/**
+ * 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 setRecordSetRequestBodyTtlDefault = 300;
+export declare const setRecordSetRequestBodyTtlMin = 0;
+export declare const setRecordSetRequestBodyTtlMax = 604800;
+export declare const setRecordSetRequestBodyValuesItemMax = 4096;
+export declare const setRecordSetRequestBodyValuesMax = 100;
+export declare const SetRecordSetRequestBody: zod.ZodObject<{
+    ttl: zod.ZodDefault<zod.ZodInt>;
+    values: zod.ZodArray<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type SetRecordSetRequestBody = zod.input<typeof SetRecordSetRequestBody>;
+export type SetRecordSetRequestBodyOutput = zod.output<typeof SetRecordSetRequestBody>;

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

@@ -0,0 +1,71 @@
+/**
+ * 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 setRecordSetRequestBodyTtlDefault = 300;
+export const setRecordSetRequestBodyTtlMin = 0;
+export const setRecordSetRequestBodyTtlMax = 604800;
+export const setRecordSetRequestBodyValuesItemMax = 4096;
+export const setRecordSetRequestBodyValuesMax = 100;
+export const SetRecordSetRequestBody = zod
+    .strictObject({
+    ttl: zod
+        .int()
+        .min(setRecordSetRequestBodyTtlMin)
+        .max(setRecordSetRequestBodyTtlMax)
+        .default(setRecordSetRequestBodyTtlDefault)
+        .describe("Time to live, in seconds. 0 leaves the choice to the provider. Providers enforce their own minimum and raise lower values to it"),
+    values: zod
+        .array(zod.string().min(1).max(setRecordSetRequestBodyValuesItemMax))
+        .min(1)
+        .max(setRecordSetRequestBodyValuesMax)
+        .describe("The final contents of the record set. Syntax as described on RecordSetResource.values"),
+})
+    .describe("`values` states the final contents of the record set. Values omitted here are removed.");

package/dist/dns/v1/generated/validators/tencentCloudConfig.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 tencentCloudConfigSecretIdMax = 256;
+export declare const tencentCloudConfigSecretKeyMax = 256;
+export declare const TencentCloudConfig: zod.ZodObject<{
+    secret_id: zod.ZodString;
+    secret_key: zod.ZodString;
+}, zod.z.core.$strict>;
+export type TencentCloudConfig = zod.input<typeof TencentCloudConfig>;
+export type TencentCloudConfigOutput = zod.output<typeof TencentCloudConfig>;

package/dist/dns/v1/generated/validators/tencentCloudConfig.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 tencentCloudConfigSecretIdMax = 256;
+export const tencentCloudConfigSecretKeyMax = 256;
+export const TencentCloudConfig = zod
+    .strictObject({
+    secret_id: zod.string().min(1).max(tencentCloudConfigSecretIdMax),
+    secret_key: zod.string().min(1).max(tencentCloudConfigSecretKeyMax),
+})
+    .describe("Tencent Cloud DNSPod credentials, created under Access Management then Access Keys");

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

@@ -0,0 +1,67 @@
+/**
+ * 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 ZoneListResponseBody: zod.ZodObject<{
+    items: zod.ZodArray<zod.ZodObject<{
+        authoritative: zod.ZodNullable<zod.ZodBoolean>;
+        credential_id: zod.ZodUUID;
+        provider: zod.ZodEnum<{
+            cloudflare: "cloudflare";
+            tencentcloud: "tencentcloud";
+            alidns: "alidns";
+            route53: "route53";
+        }>;
+        zone: zod.ZodString;
+    }, zod.z.core.$strict>>;
+    stale: zod.ZodBoolean;
+}, zod.z.core.$strict>;
+export type ZoneListResponseBody = zod.input<typeof ZoneListResponseBody>;
+export type ZoneListResponseBodyOutput = zod.output<typeof ZoneListResponseBody>;