@leaflow/sdk 0.0.0-dev.35.g30ba751 → 0.0.0-dev.353.g74313e0

package/dist/support/v1/generated/validators/listTicketsParams.zod.js

@@ -0,0 +1,71 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { TicketPriority } from "./ticketPriority.zod.js";
+import { TicketStatus } from "./ticketStatus.zod.js";
+export const listTicketsParamsLimitDefault = 50;
+export const listTicketsParamsLimitMax = 200;
+export const listTicketsParamsOffsetDefault = 0;
+export const listTicketsParamsOffsetMin = 0;
+export const listTicketsParamsOffsetMax = 10000;
+export const listTicketsParamsKeywordMax = 128;
+export const ListTicketsParams = zod.strictObject({
+    limit: zod.int().min(1).max(listTicketsParamsLimitMax).default(listTicketsParamsLimitDefault),
+    offset: zod
+        .int()
+        .min(listTicketsParamsOffsetMin)
+        .max(listTicketsParamsOffsetMax)
+        .default(listTicketsParamsOffsetDefault),
+    status: TicketStatus.optional(),
+    priority: TicketPriority.optional(),
+    category_id: zod.uuid().optional(),
+    keyword: zod.string().max(listTicketsParamsKeywordMax).optional(),
+});

package/dist/support/v1/generated/validators/maintenanceImpact.zod.d.ts

@@ -0,0 +1,59 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const MaintenanceImpact: zod.ZodEnum<{
+    PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+    MAJOR_OUTAGE: "MAJOR_OUTAGE";
+    NONE: "NONE";
+    DEGRADED: "DEGRADED";
+}>;
+export type MaintenanceImpact = zod.input<typeof MaintenanceImpact>;
+export type MaintenanceImpactOutput = zod.output<typeof MaintenanceImpact>;

package/dist/support/v1/generated/validators/maintenanceImpact.zod.js

@@ -0,0 +1,54 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const MaintenanceImpact = zod
+    .enum(["NONE", "DEGRADED", "PARTIAL_OUTAGE", "MAJOR_OUTAGE"])
+    .describe("What users should expect during the window.");

package/dist/support/v1/generated/validators/maintenanceResource.zod.d.ts

@@ -0,0 +1,75 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const MaintenanceResource: zod.ZodObject<{
+    body: zod.ZodString;
+    completed_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    components: zod.ZodArray<zod.ZodString>;
+    id: zod.ZodUUID;
+    impact: zod.ZodEnum<{
+        PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+        MAJOR_OUTAGE: "MAJOR_OUTAGE";
+        NONE: "NONE";
+        DEGRADED: "DEGRADED";
+    }>;
+    scheduled_for: zod.z.ZodISODateTime;
+    scheduled_until: zod.z.ZodISODateTime;
+    started_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    status: zod.ZodEnum<{
+        SCHEDULED: "SCHEDULED";
+        IN_PROGRESS: "IN_PROGRESS";
+        COMPLETED: "COMPLETED";
+        CANCELLED: "CANCELLED";
+    }>;
+    title: zod.ZodString;
+}, zod.z.core.$strict>;
+export type MaintenanceResource = zod.input<typeof MaintenanceResource>;
+export type MaintenanceResourceOutput = zod.output<typeof MaintenanceResource>;

package/dist/support/v1/generated/validators/maintenanceResource.zod.js

@@ -0,0 +1,75 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { MaintenanceImpact } from "./maintenanceImpact.zod.js";
+import { MaintenanceStatus } from "./maintenanceStatus.zod.js";
+export const MaintenanceResource = zod
+    .strictObject({
+    body: zod.string().describe("Markdown"),
+    completed_at: zod.iso
+        .datetime({ offset: true })
+        .nullable()
+        .describe("When the maintenance actually finished; null until it does"),
+    components: zod
+        .array(zod.string())
+        .describe("What this maintenance affects. The names are those used by the services concerned"),
+    id: zod.uuid(),
+    impact: MaintenanceImpact,
+    scheduled_for: zod.iso.datetime({ offset: true }).describe("The announced start"),
+    scheduled_until: zod.iso.datetime({ offset: true }).describe("The announced end"),
+    started_at: zod.iso
+        .datetime({ offset: true })
+        .nullable()
+        .describe("When the maintenance actually started; null until it does"),
+    status: MaintenanceStatus,
+    title: zod.string(),
+})
+    .describe("A scheduled maintenance notice published by platform operators.");

package/dist/support/v1/generated/validators/maintenanceStatus.zod.d.ts

@@ -0,0 +1,59 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const MaintenanceStatus: zod.ZodEnum<{
+    SCHEDULED: "SCHEDULED";
+    IN_PROGRESS: "IN_PROGRESS";
+    COMPLETED: "COMPLETED";
+    CANCELLED: "CANCELLED";
+}>;
+export type MaintenanceStatus = zod.input<typeof MaintenanceStatus>;
+export type MaintenanceStatusOutput = zod.output<typeof MaintenanceStatus>;

package/dist/support/v1/generated/validators/maintenanceStatus.zod.js

@@ -0,0 +1,54 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const MaintenanceStatus = zod
+    .enum(["SCHEDULED", "IN_PROGRESS", "COMPLETED", "CANCELLED"])
+    .describe("`SCHEDULED` has been announced but has not started. `IN_PROGRESS` is under way. `COMPLETED`\nhas finished. `CANCELLED` was announced and then called off, and never took place.");

package/dist/support/v1/generated/validators/maintenanceTimelineEntryResource.zod.d.ts

@@ -0,0 +1,70 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const MaintenanceTimelineEntryResource: zod.ZodObject<{
+    body: zod.ZodString;
+    created_at: zod.z.ZodISODateTime;
+    id: zod.ZodUUID;
+    impact: zod.ZodUnion<readonly [zod.ZodEnum<{
+        PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+        MAJOR_OUTAGE: "MAJOR_OUTAGE";
+        NONE: "NONE";
+        DEGRADED: "DEGRADED";
+    }>, zod.ZodNull]>;
+    status: zod.ZodUnion<readonly [zod.ZodEnum<{
+        SCHEDULED: "SCHEDULED";
+        IN_PROGRESS: "IN_PROGRESS";
+        COMPLETED: "COMPLETED";
+        CANCELLED: "CANCELLED";
+    }>, zod.ZodNull]>;
+}, zod.z.core.$strict>;
+export type MaintenanceTimelineEntryResource = zod.input<typeof MaintenanceTimelineEntryResource>;
+export type MaintenanceTimelineEntryResourceOutput = zod.output<typeof MaintenanceTimelineEntryResource>;

package/dist/support/v1/generated/validators/maintenanceTimelineEntryResource.zod.js

@@ -0,0 +1,66 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { MaintenanceImpact } from "./maintenanceImpact.zod.js";
+import { MaintenanceStatus } from "./maintenanceStatus.zod.js";
+export const MaintenanceTimelineEntryResource = zod
+    .strictObject({
+    body: zod.string(),
+    created_at: zod.iso.datetime({ offset: true }),
+    id: zod.uuid(),
+    impact: zod
+        .union([MaintenanceImpact, zod.null()])
+        .describe("The impact this update declared; null when the update did not change it"),
+    status: zod
+        .union([MaintenanceStatus, zod.null()])
+        .describe("The state this update moved the maintenance to; null when the update did not change it"),
+})
+    .describe("One update posted during a maintenance.");

package/dist/support/v1/generated/validators/noticeMaintenanceResource.zod.d.ts

@@ -0,0 +1,74 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const NoticeMaintenanceResource: zod.ZodObject<{
+    body: zod.ZodString;
+    components: zod.ZodArray<zod.ZodString>;
+    id: zod.ZodUUID;
+    impact: zod.ZodEnum<{
+        PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+        MAJOR_OUTAGE: "MAJOR_OUTAGE";
+        NONE: "NONE";
+        DEGRADED: "DEGRADED";
+    }>;
+    scheduled_for: zod.z.ZodISODateTime;
+    scheduled_until: zod.z.ZodISODateTime;
+    started_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    status: zod.ZodEnum<{
+        SCHEDULED: "SCHEDULED";
+        IN_PROGRESS: "IN_PROGRESS";
+        COMPLETED: "COMPLETED";
+        CANCELLED: "CANCELLED";
+    }>;
+    title: zod.ZodString;
+}, zod.z.core.$strict>;
+export type NoticeMaintenanceResource = zod.input<typeof NoticeMaintenanceResource>;
+export type NoticeMaintenanceResourceOutput = zod.output<typeof NoticeMaintenanceResource>;