@leaflow/sdk 0.108.0 → 0.109.0

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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