@leaflow/sdk 0.0.0-dev.541.g49c432c → 0.0.0-dev.546.gd7d0a9b

package/dist/notification/v1/generated/validators/notificationScope.zod.d.ts

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/notificationScope.zod.js

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/notificationSeverity.zod.d.ts

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/notificationSeverity.zod.js

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/notificationTypeDescriptor.zod.d.ts

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/notificationTypeDescriptor.zod.js

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/notificationTypeListResponseBody.zod.d.ts

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/notificationTypeListResponseBody.zod.js

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

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

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

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

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/preferencesResource.zod.d.ts

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/preferencesResource.zod.js

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/typePreferenceListResponseBody.zod.d.ts

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/typePreferenceListResponseBody.zod.js

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/typePreferenceResource.zod.d.ts

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/typePreferenceResource.zod.js

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/unreadCountResource.zod.d.ts

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/unreadCountResource.zod.js

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/updateChannelRequestBody.zod.d.ts

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/updateChannelRequestBody.zod.js

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/updatePreferencesRequestBody.zod.d.ts

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/updatePreferencesRequestBody.zod.js

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/updateTypePreferenceParams.zod.d.ts

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/updateTypePreferenceParams.zod.js

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/updateTypePreferenceRequestBody.zod.d.ts

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/notification/v1/generated/validators/updateTypePreferenceRequestBody.zod.js

@@ -50,13 +50,6 @@
  * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
  * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
  * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/routes.d.ts

@@ -4629,22 +4629,6 @@ export declare const routes: readonly [{
     readonly operationId: "verify-user-channel";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://notification.leaflow.cloud";
-}, {
-    readonly service: "notification";
-    readonly contract: "notification";
-    readonly method: "GET";
-    readonly path: "/api/v1/credentials/{ticketId}";
-    readonly operationId: "describe-credential-ticket";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://notification.leaflow.cloud";
-}, {
-    readonly service: "notification";
-    readonly contract: "notification";
-    readonly method: "POST";
-    readonly path: "/api/v1/credentials/{ticketId}:reveal";
-    readonly operationId: "reveal-credential";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://notification.leaflow.cloud";
 }, {
     readonly service: "support";
     readonly contract: "support";

package/dist/routes.js

@@ -5208,24 +5208,6 @@ export const routes = [
         securityScheme: "ScopedToken",
         upstreamUrl: "https://notification.leaflow.cloud",
     },
-    {
-        service: "notification",
-        contract: "notification",
-        method: "GET",
-        path: "/api/v1/credentials/{ticketId}",
-        operationId: "describe-credential-ticket",
-        securityScheme: "ScopedToken",
-        upstreamUrl: "https://notification.leaflow.cloud",
-    },
-    {
-        service: "notification",
-        contract: "notification",
-        method: "POST",
-        path: "/api/v1/credentials/{ticketId}:reveal",
-        operationId: "reveal-credential",
-        securityScheme: "ScopedToken",
-        upstreamUrl: "https://notification.leaflow.cloud",
-    },
     {
         service: "support",
         contract: "support",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leaflow/sdk",
-  "version": "0.0.0-dev.541.g49c432c",
+  "version": "0.0.0-dev.546.gd7d0a9b",
   "description": "Leaflow 平台 API 的 TypeScript SDK",
   "license": "MIT",
   "repository": {

package/dist/notification/v1/generated/validators/credentialSubjectKind.zod.d.ts

@@ -1,67 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Notification API
- * Read the notifications this platform has sent you, and choose where each kind of notification
- * is delivered.
- *
- * Every service on the platform reports events here rather than contacting you directly. This
- * API is the single place where those events are read, and the single place where delivery is
- * configured.
- *
- * ## 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. Listing operations return everything addressed to you across every project by
- * default, because a notification is addressed to a person rather than to a project; pass
- * `scope=current_project` to narrow the result to the project in the token.
- *
- * ## Conventions
- *
- * - **Notifications are typed, and the type determines who receives it.** A type such as
- *   `compute.instance.provisioned` is addressed to whoever created the instance, while
- *   `monitoring.alert.raised` is addressed to every member of the project. The full catalogue is
- *   available from `GET /api/v1/notification-types` and is stable: a type identifier is never
- *   reused for a different event.
- * - **Text is rendered at read time from the language on your preferences.** Changing the
- *   language changes the text of everything already in the inbox. Messages already delivered by
- *   email or to an outbound channel are not rewritten, because they have already been sent.
- * - **Times inside rendered text are stated in UTC and say so.** There is no time zone setting.
- *   Clients that can determine the reader's time zone should present `created_at`, `occurred_at`
- *   and the timestamps in `params` — all of which are RFC 3339 — in local time instead. Email
- *   cannot do this, which is why the text it carries is explicit about being UTC.
- * - **Some types must reach you, and those cannot be muted or removed from email.** They are
- *   marked `mandatory` in the catalogue: types you would only find out about by signing in, when
- *   not finding out costs you something — a suspension, a deletion, a credential that expires.
- *   Everything else about them is still configurable, including adding channels of your own.
- * - **Deleting a preference restores the default; it does not turn the type off.** To stop
- *   receiving a type, set `muted` on it.
- * - **Outbound channels deliver nothing until they are verified.** Registering a channel does not
- *   contact it. Verification is a separate operation that sends one message, and only a channel
- *   that has acknowledged it receives anything afterwards.
- * - **Channel endpoints are never returned.** No operation, including the one that registers
- *   them, returns the address that was submitted. A channel entered incorrectly must be deleted
- *   and registered again.
- *
- * ## Rate and volume
- *
- * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
- * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
- * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export declare const CredentialSubjectKind: zod.ZodEnum<{
-    compute_instance: "compute_instance";
-}>;
-export type CredentialSubjectKind = zod.input<typeof CredentialSubjectKind>;
-export type CredentialSubjectKindOutput = zod.output<typeof CredentialSubjectKind>;

package/dist/notification/v1/generated/validators/credentialSubjectKind.zod.js

@@ -1,65 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Notification API
- * Read the notifications this platform has sent you, and choose where each kind of notification
- * is delivered.
- *
- * Every service on the platform reports events here rather than contacting you directly. This
- * API is the single place where those events are read, and the single place where delivery is
- * configured.
- *
- * ## 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. Listing operations return everything addressed to you across every project by
- * default, because a notification is addressed to a person rather than to a project; pass
- * `scope=current_project` to narrow the result to the project in the token.
- *
- * ## Conventions
- *
- * - **Notifications are typed, and the type determines who receives it.** A type such as
- *   `compute.instance.provisioned` is addressed to whoever created the instance, while
- *   `monitoring.alert.raised` is addressed to every member of the project. The full catalogue is
- *   available from `GET /api/v1/notification-types` and is stable: a type identifier is never
- *   reused for a different event.
- * - **Text is rendered at read time from the language on your preferences.** Changing the
- *   language changes the text of everything already in the inbox. Messages already delivered by
- *   email or to an outbound channel are not rewritten, because they have already been sent.
- * - **Times inside rendered text are stated in UTC and say so.** There is no time zone setting.
- *   Clients that can determine the reader's time zone should present `created_at`, `occurred_at`
- *   and the timestamps in `params` — all of which are RFC 3339 — in local time instead. Email
- *   cannot do this, which is why the text it carries is explicit about being UTC.
- * - **Some types must reach you, and those cannot be muted or removed from email.** They are
- *   marked `mandatory` in the catalogue: types you would only find out about by signing in, when
- *   not finding out costs you something — a suspension, a deletion, a credential that expires.
- *   Everything else about them is still configurable, including adding channels of your own.
- * - **Deleting a preference restores the default; it does not turn the type off.** To stop
- *   receiving a type, set `muted` on it.
- * - **Outbound channels deliver nothing until they are verified.** Registering a channel does not
- *   contact it. Verification is a separate operation that sends one message, and only a channel
- *   that has acknowledged it receives anything afterwards.
- * - **Channel endpoints are never returned.** No operation, including the one that registers
- *   them, returns the address that was submitted. A channel entered incorrectly must be deleted
- *   and registered again.
- *
- * ## Rate and volume
- *
- * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
- * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
- * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export const CredentialSubjectKind = zod
-    .enum(["compute_instance"])
-    .describe("What the credential belongs to.");