@leaflow/sdk 0.107.0 → 0.109.0

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

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

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

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

package/dist/gen/dns/v1/models/credentialResource.d.ts

@@ -1,82 +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 { CredentialStatus } from "./credentialStatus.js";
-import type { Provider } from "./provider.js";
-/**
- * A registered provider credential. The credential material itself is never included.
- */
-export interface CredentialResource {
-    created_at: string;
-    /** Equal fingerprints denote the same credential material */
-    fingerprint: string;
-    id: string;
-    /**
-     * When the credential was last confirmed to work; null if it never has
-     * @nullable
-     */
-    last_verified_at: string | null;
-    /**
-     * Why the most recent check failed; null if the most recent check succeeded
-     * @nullable
-     */
-    last_verify_error: string | null;
-    name: string;
-    provider: Provider;
-    /** A partially masked fragment of the credential, for visual identification only */
-    redacted: string;
-    status: CredentialStatus;
-    /**
-     * When the credential was suspended because the project was suspended; null if it was not. Cleared when the project is restored
-     * @nullable
-     */
-    suspended_at: string | null;
-    updated_at: string;
-}

package/dist/gen/dns/v1/models/credentialResource.js

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

package/dist/gen/dns/v1/models/credentialStatus.d.ts

@@ -1,61 +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
- */
-/**
- * `active` is usable. `disabled` means the platform has disabled this credential and requires
- * contact with support.
- *
- * A project that has been suspended is reported separately, in `suspended_at`.
- */
-export type CredentialStatus = (typeof CredentialStatus)[keyof typeof CredentialStatus];
-export declare const CredentialStatus: {
-    readonly active: "active";
-    readonly disabled: "disabled";
-};

package/dist/gen/dns/v1/models/credentialStatus.js

@@ -1,54 +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 CredentialStatus = {
-    active: "active",
-    disabled: "disabled",
-};

package/dist/gen/dns/v1/models/deleteRecordSetParams.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 DeleteRecordSetParams = {
-    /**
-     * Which credential to use. When omitted, the credential is determined from the domain; see ZONE_AMBIGUOUS
-     */
-    credential_id?: string;
-};

package/dist/gen/dns/v1/models/deleteRecordSetParams.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/gen/dns/v1/models/error.d.ts

@@ -1,61 +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 { ErrorMeta } from "./errorMeta.js";
-export interface Error {
-    code?: string;
-    message: string;
-    /**
-     * What a given `code` carries alongside the message. The keys depend on the code,
-     * and a client that does not recognise one ignores it.
-     */
-    meta?: ErrorMeta;
-    status: number;
-}

package/dist/gen/dns/v1/models/error.js

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

package/dist/gen/dns/v1/models/errorMeta.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
- */
-/**
- * What a given `code` carries alongside the message. The keys depend on the code,
- * and a client that does not recognise one ignores it.
- */
-export type ErrorMeta = {
-    [key: string]: unknown;
-};

package/dist/gen/dns/v1/models/errorMeta.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/gen/dns/v1/models/lengthAwarePageCredentialResource.d.ts

@@ -1,61 +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 { CredentialResource } from "./credentialResource.js";
-export interface LengthAwarePageCredentialResource {
-    /** The contents of this page */
-    items: CredentialResource[];
-    /** Maximum items per page, echoing the value in the request */
-    limit: number;
-    /** Items skipped, echoing the value in the request */
-    offset: number;
-    /** Total number of matching items, not only those in this page */
-    total: number;
-}

package/dist/gen/dns/v1/models/lengthAwarePageCredentialResource.js

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