@leaflow/sdk 0.0.0-dev.29.g8fe6a71 → 0.0.0-dev.293.g578f043

package/dist/monitoring/v1/generated/validators/publishStatusPageIncidentRequestBody.zod.d.ts

@@ -0,0 +1,53 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const publishStatusPageIncidentRequestBodyIncidentStatusDefault = "INVESTIGATING";
+export declare const publishStatusPageIncidentRequestBodyNameMax = 255;
+export declare const PublishStatusPageIncidentRequestBody: zod.ZodObject<{
+    body: zod.ZodString;
+    components: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
+        component_id: zod.ZodUUID;
+        status: zod.ZodOptional<zod.ZodEnum<{
+            OPERATIONAL: "OPERATIONAL";
+            DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+            PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+            MAJOR_OUTAGE: "MAJOR_OUTAGE";
+            UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+        }>>;
+    }, zod.z.core.$strict>>>;
+    impact: zod.ZodOptional<zod.ZodEnum<{
+        NONE: "NONE";
+        MINOR: "MINOR";
+        MAJOR: "MAJOR";
+        CRITICAL: "CRITICAL";
+    }>>;
+    incident_status: zod.ZodDefault<zod.ZodEnum<{
+        RESOLVED: "RESOLVED";
+        INVESTIGATING: "INVESTIGATING";
+        IDENTIFIED: "IDENTIFIED";
+        MONITORING: "MONITORING";
+    }>>;
+    name: zod.ZodString;
+    published_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+    started_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+}, zod.z.core.$strict>;
+export type PublishStatusPageIncidentRequestBody = zod.input<typeof PublishStatusPageIncidentRequestBody>;
+export type PublishStatusPageIncidentRequestBodyOutput = zod.output<typeof PublishStatusPageIncidentRequestBody>;

package/dist/monitoring/v1/generated/validators/publishStatusPageIncidentRequestBody.zod.js

@@ -0,0 +1,48 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { StatusPageIncidentComponentRequest } from "./statusPageIncidentComponentRequest.zod.js";
+export const publishStatusPageIncidentRequestBodyIncidentStatusDefault = `INVESTIGATING`;
+export const publishStatusPageIncidentRequestBodyNameMax = 255;
+export const PublishStatusPageIncidentRequestBody = zod.strictObject({
+    body: zod.string().min(1).describe("Body of the first update. Plain text"),
+    components: zod.array(StatusPageIncidentComponentRequest).optional(),
+    impact: zod
+        .enum(["NONE", "MINOR", "MAJOR", "CRITICAL"])
+        .optional()
+        .describe("Empty derives the impact from the affected components"),
+    incident_status: zod
+        .enum(["INVESTIGATING", "IDENTIFIED", "MONITORING", "RESOLVED"])
+        .default(publishStatusPageIncidentRequestBodyIncidentStatusDefault),
+    name: zod
+        .string()
+        .min(1)
+        .max(publishStatusPageIncidentRequestBodyNameMax)
+        .describe("The public title"),
+    published_at: zod.iso
+        .datetime({ offset: true })
+        .optional()
+        .describe("Empty selects the current moment. Backfilling a past incident sets it in the past"),
+    started_at: zod.iso
+        .datetime({ offset: true })
+        .optional()
+        .describe("When the incident began. Empty uses the publication time"),
+});

package/dist/monitoring/v1/generated/validators/putMaintenanceWindowRequestBody.zod.d.ts

@@ -0,0 +1,46 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const putMaintenanceWindowRequestBodyDescriptionMax = 2000;
+export declare const putMaintenanceWindowRequestBodyNameMax = 128;
+export declare const putMaintenanceWindowRequestBodyTimezoneMax = 64;
+export declare const PutMaintenanceWindowRequestBody: zod.ZodObject<{
+    active_since: zod.z.ZodISODateTime;
+    active_till: zod.z.ZodISODateTime;
+    description: zod.ZodOptional<zod.ZodString>;
+    name: zod.ZodString;
+    period: zod.ZodObject<{
+        duration_seconds: zod.ZodOptional<zod.ZodInt>;
+        every: zod.ZodOptional<zod.ZodInt>;
+        kind: zod.ZodEnum<{
+            ONCE: "ONCE";
+            DAILY: "DAILY";
+            WEEKLY: "WEEKLY";
+        }>;
+        start_time_seconds: zod.ZodOptional<zod.ZodInt>;
+        starts_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+        weekdays: zod.ZodOptional<zod.ZodInt>;
+    }, zod.z.core.$strict>;
+    server_ids: zod.ZodOptional<zod.ZodNullable<zod.ZodArray<zod.ZodString>>>;
+    timezone: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type PutMaintenanceWindowRequestBody = zod.input<typeof PutMaintenanceWindowRequestBody>;
+export type PutMaintenanceWindowRequestBodyOutput = zod.output<typeof PutMaintenanceWindowRequestBody>;

package/dist/monitoring/v1/generated/validators/putMaintenanceWindowRequestBody.zod.js

@@ -0,0 +1,40 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { MaintenancePeriodRequest } from "./maintenancePeriodRequest.zod.js";
+export const putMaintenanceWindowRequestBodyDescriptionMax = 2000;
+export const putMaintenanceWindowRequestBodyNameMax = 128;
+export const putMaintenanceWindowRequestBodyTimezoneMax = 64;
+export const PutMaintenanceWindowRequestBody = zod.strictObject({
+    active_since: zod.iso
+        .datetime({ offset: true })
+        .describe("Start of the period in which the rule is effective"),
+    active_till: zod.iso.datetime({ offset: true }),
+    description: zod.string().max(putMaintenanceWindowRequestBodyDescriptionMax).optional(),
+    name: zod.string().min(1).max(putMaintenanceWindowRequestBodyNameMax),
+    period: MaintenancePeriodRequest,
+    server_ids: zod.array(zod.string()).nullish(),
+    timezone: zod
+        .string()
+        .max(putMaintenanceWindowRequestBodyTimezoneMax)
+        .optional()
+        .describe("IANA name such as Asia/Shanghai. Empty uses the configured default"),
+});

package/dist/monitoring/v1/generated/validators/putSLORequestBody.zod.d.ts

@@ -0,0 +1,54 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const putSLORequestBodyNameMax = 128;
+export declare const putSLORequestBodySloPercentMin = 0;
+export declare const putSLORequestBodySloPercentMax = 100;
+export declare const putSLORequestBodyTimezoneMax = 64;
+export declare const PutSLORequestBody: zod.ZodObject<{
+    effective_from: zod.ZodOptional<zod.z.ZodISODateTime>;
+    min_severity: zod.ZodEnum<{
+        INFORMATION: "INFORMATION";
+        WARNING: "WARNING";
+        AVERAGE: "AVERAGE";
+        HIGH: "HIGH";
+        DISASTER: "DISASTER";
+        ANY: "ANY";
+    }>;
+    name: zod.ZodString;
+    period: zod.ZodOptional<zod.ZodEnum<{
+        DAILY: "DAILY";
+        WEEKLY: "WEEKLY";
+        MONTHLY: "MONTHLY";
+        QUARTERLY: "QUARTERLY";
+        ANNUALLY: "ANNUALLY";
+    }>>;
+    schedule: zod.ZodOptional<zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        end_time_seconds: zod.ZodOptional<zod.ZodInt>;
+        start_time_seconds: zod.ZodOptional<zod.ZodInt>;
+        weekdays: zod.ZodInt;
+    }, zod.z.core.$strict>>>>;
+    slo_id: zod.ZodUUID;
+    slo_percent: zod.ZodNumber;
+    timezone: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type PutSLORequestBody = zod.input<typeof PutSLORequestBody>;
+export type PutSLORequestBodyOutput = zod.output<typeof PutSLORequestBody>;

package/dist/monitoring/v1/generated/validators/putSLORequestBody.zod.js

@@ -0,0 +1,47 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { ScheduleWindowRequest } from "./scheduleWindowRequest.zod.js";
+export const putSLORequestBodyNameMax = 128;
+export const putSLORequestBodySloPercentMin = 0;
+export const putSLORequestBodySloPercentMax = 100;
+export const putSLORequestBodyTimezoneMax = 64;
+export const PutSLORequestBody = zod.strictObject({
+    effective_from: zod.iso.datetime({ offset: true }).optional(),
+    min_severity: zod.enum(["ANY", "INFORMATION", "WARNING", "AVERAGE", "HIGH", "DISASTER"]),
+    name: zod.string().min(1).max(putSLORequestBodyNameMax),
+    period: zod
+        .enum(["DAILY", "WEEKLY", "MONTHLY", "QUARTERLY", "ANNUALLY"])
+        .optional()
+        .describe("Empty selects monthly"),
+    schedule: zod.array(ScheduleWindowRequest).nullish(),
+    slo_id: zod.uuid(),
+    slo_percent: zod
+        .number()
+        .min(putSLORequestBodySloPercentMin)
+        .max(putSLORequestBodySloPercentMax)
+        .describe("Target availability, such as 99.9. At most four decimal places"),
+    timezone: zod
+        .string()
+        .max(putSLORequestBodyTimezoneMax)
+        .optional()
+        .describe("Determines the boundaries of each reporting period, that is, the moment each period begins"),
+});

package/dist/monitoring/v1/generated/validators/putStatusPageComponentRequestBody.zod.d.ts

@@ -0,0 +1,44 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const putStatusPageComponentRequestBodyAutoStatusMinSeverityDefault = "AVERAGE";
+export declare const putStatusPageComponentRequestBodyDescriptionMax = 2000;
+export declare const putStatusPageComponentRequestBodyNameMax = 128;
+export declare const putStatusPageComponentRequestBodyOnlyShowIfDegradedDefault = false;
+export declare const putStatusPageComponentRequestBodyShowUptimeDefault = true;
+export declare const PutStatusPageComponentRequestBody: zod.ZodObject<{
+    auto_status_min_severity: zod.ZodDefault<zod.ZodEnum<{
+        INFORMATION: "INFORMATION";
+        WARNING: "WARNING";
+        AVERAGE: "AVERAGE";
+        HIGH: "HIGH";
+        DISASTER: "DISASTER";
+        ANY: "ANY";
+    }>>;
+    description: zod.ZodOptional<zod.ZodString>;
+    group_id: zod.ZodOptional<zod.ZodUUID>;
+    name: zod.ZodString;
+    only_show_if_degraded: zod.ZodDefault<zod.ZodBoolean>;
+    show_uptime: zod.ZodDefault<zod.ZodBoolean>;
+    started_on: zod.ZodOptional<zod.z.ZodISODateTime>;
+}, zod.z.core.$strict>;
+export type PutStatusPageComponentRequestBody = zod.input<typeof PutStatusPageComponentRequestBody>;
+export type PutStatusPageComponentRequestBodyOutput = zod.output<typeof PutStatusPageComponentRequestBody>;

package/dist/monitoring/v1/generated/validators/putStatusPageComponentRequestBody.zod.js

@@ -0,0 +1,47 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const putStatusPageComponentRequestBodyAutoStatusMinSeverityDefault = `AVERAGE`;
+export const putStatusPageComponentRequestBodyDescriptionMax = 2000;
+export const putStatusPageComponentRequestBodyNameMax = 128;
+export const putStatusPageComponentRequestBodyOnlyShowIfDegradedDefault = false;
+export const putStatusPageComponentRequestBodyShowUptimeDefault = true;
+export const PutStatusPageComponentRequestBody = zod.strictObject({
+    auto_status_min_severity: zod
+        .enum(["ANY", "INFORMATION", "WARNING", "AVERAGE", "HIGH", "DISASTER"])
+        .default(putStatusPageComponentRequestBodyAutoStatusMinSeverityDefault)
+        .describe("Alerts below this severity do not change the status of this row"),
+    description: zod.string().max(putStatusPageComponentRequestBodyDescriptionMax).optional(),
+    group_id: zod.uuid().optional().describe("Empty leaves the component ungrouped"),
+    name: zod
+        .string()
+        .min(1)
+        .max(putStatusPageComponentRequestBodyNameMax)
+        .describe("Customer-facing copy; appears verbatim on the public page"),
+    only_show_if_degraded: zod
+        .boolean()
+        .default(putStatusPageComponentRequestBodyOnlyShowIfDegradedDefault),
+    show_uptime: zod.boolean().default(putStatusPageComponentRequestBodyShowUptimeDefault),
+    started_on: zod.iso
+        .datetime({ offset: true })
+        .optional()
+        .describe("Meaningful only at creation and immutable afterwards. Empty selects the current moment"),
+});

package/dist/monitoring/v1/generated/validators/putStatusPageComponentSourcesRequestBody.zod.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const PutStatusPageComponentSourcesRequestBody: zod.ZodObject<{
+    servers: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
+        server_id: zod.ZodUUID;
+    }, zod.z.core.$strict>>>;
+    web_checks: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
+        show_url: zod.ZodDefault<zod.ZodBoolean>;
+        web_check_id: zod.ZodUUID;
+    }, zod.z.core.$strict>>>;
+}, zod.z.core.$strict>;
+export type PutStatusPageComponentSourcesRequestBody = zod.input<typeof PutStatusPageComponentSourcesRequestBody>;
+export type PutStatusPageComponentSourcesRequestBodyOutput = zod.output<typeof PutStatusPageComponentSourcesRequestBody>;

package/dist/monitoring/v1/generated/validators/putStatusPageComponentSourcesRequestBody.zod.js

@@ -0,0 +1,29 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { StatusPageComponentSourceServer } from "./statusPageComponentSourceServer.zod.js";
+import { StatusPageComponentSourceWebCheck } from "./statusPageComponentSourceWebCheck.zod.js";
+export const PutStatusPageComponentSourcesRequestBody = zod
+    .strictObject({
+    servers: zod.array(StatusPageComponentSourceServer).optional(),
+    web_checks: zod.array(StatusPageComponentSourceWebCheck).optional(),
+})
+    .describe("Submits the complete set; anything not listed is unbound");

package/dist/monitoring/v1/generated/validators/putStatusPageDomainRequestBody.zod.d.ts

@@ -0,0 +1,27 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const putStatusPageDomainRequestBodyDomainMax = 253;
+export declare const PutStatusPageDomainRequestBody: zod.ZodObject<{
+    domain: zod.ZodString;
+}, zod.z.core.$strict>;
+export type PutStatusPageDomainRequestBody = zod.input<typeof PutStatusPageDomainRequestBody>;
+export type PutStatusPageDomainRequestBodyOutput = zod.output<typeof PutStatusPageDomainRequestBody>;

package/dist/monitoring/v1/generated/validators/putStatusPageDomainRequestBody.zod.js

@@ -0,0 +1,29 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const putStatusPageDomainRequestBodyDomainMax = 253;
+export const PutStatusPageDomainRequestBody = zod.strictObject({
+    domain: zod
+        .string()
+        .min(1)
+        .max(putStatusPageDomainRequestBodyDomainMax)
+        .describe("Your own domain, such as status.acme.com. It must already point at the status page by CNAME"),
+});

package/dist/monitoring/v1/generated/validators/putStatusPageGroupOrderRequestBody.zod.d.ts

@@ -0,0 +1,26 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const PutStatusPageGroupOrderRequestBody: zod.ZodObject<{
+    component_ids: zod.ZodArray<zod.ZodUUID>;
+}, zod.z.core.$strict>;
+export type PutStatusPageGroupOrderRequestBody = zod.input<typeof PutStatusPageGroupOrderRequestBody>;
+export type PutStatusPageGroupOrderRequestBodyOutput = zod.output<typeof PutStatusPageGroupOrderRequestBody>;

package/dist/monitoring/v1/generated/validators/putStatusPageGroupOrderRequestBody.zod.js

@@ -0,0 +1,24 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const PutStatusPageGroupOrderRequestBody = zod.strictObject({
+    component_ids: zod.array(zod.uuid()),
+});

package/dist/monitoring/v1/generated/validators/putStatusPageGroupRequestBody.zod.d.ts

@@ -0,0 +1,31 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const putStatusPageGroupRequestBodyCollapsedDefault = true;
+export declare const putStatusPageGroupRequestBodyDescriptionMax = 2000;
+export declare const putStatusPageGroupRequestBodyNameMax = 128;
+export declare const PutStatusPageGroupRequestBody: zod.ZodObject<{
+    collapsed: zod.ZodDefault<zod.ZodBoolean>;
+    description: zod.ZodOptional<zod.ZodString>;
+    name: zod.ZodString;
+}, zod.z.core.$strict>;
+export type PutStatusPageGroupRequestBody = zod.input<typeof PutStatusPageGroupRequestBody>;
+export type PutStatusPageGroupRequestBodyOutput = zod.output<typeof PutStatusPageGroupRequestBody>;

package/dist/monitoring/v1/generated/validators/putStatusPageGroupRequestBody.zod.js

@@ -0,0 +1,29 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const putStatusPageGroupRequestBodyCollapsedDefault = true;
+export const putStatusPageGroupRequestBodyDescriptionMax = 2000;
+export const putStatusPageGroupRequestBodyNameMax = 128;
+export const PutStatusPageGroupRequestBody = zod.strictObject({
+    collapsed: zod.boolean().default(putStatusPageGroupRequestBodyCollapsedDefault),
+    description: zod.string().max(putStatusPageGroupRequestBodyDescriptionMax).optional(),
+    name: zod.string().min(1).max(putStatusPageGroupRequestBodyNameMax),
+});