@leaflow/sdk 0.0.0-dev.29.g8fe6a71 → 0.0.0-dev.291.gcde7444

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

@@ -0,0 +1,71 @@
+/**
+ * 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 StatusPageIncidentResource: zod.ZodObject<{
+    impact: zod.ZodEnum<{
+        NONE: "NONE";
+        MINOR: "MINOR";
+        MAJOR: "MAJOR";
+        CRITICAL: "CRITICAL";
+    }>;
+    incident_id: zod.ZodUUID;
+    incident_status: zod.ZodEnum<{
+        RESOLVED: "RESOLVED";
+        INVESTIGATING: "INVESTIGATING";
+        IDENTIFIED: "IDENTIFIED";
+        MONITORING: "MONITORING";
+    }>;
+    name: zod.ZodString;
+    published_at: zod.z.ZodISODateTime;
+    resolved_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    started_at: zod.z.ZodISODateTime;
+    updates: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        affected_components: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+            component_id: zod.ZodUUID;
+            component_name: zod.ZodString;
+            new_status: zod.ZodEnum<{
+                OPERATIONAL: "OPERATIONAL";
+                DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+                PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+                MAJOR_OUTAGE: "MAJOR_OUTAGE";
+                UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+            }>;
+            old_status: zod.ZodEnum<{
+                OPERATIONAL: "OPERATIONAL";
+                DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+                PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+                MAJOR_OUTAGE: "MAJOR_OUTAGE";
+                UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+            }>;
+        }, zod.z.core.$strict>>>;
+        body: zod.ZodString;
+        incident_status: zod.ZodEnum<{
+            RESOLVED: "RESOLVED";
+            INVESTIGATING: "INVESTIGATING";
+            IDENTIFIED: "IDENTIFIED";
+            MONITORING: "MONITORING";
+        }>;
+        published_at: zod.z.ZodISODateTime;
+        update_id: zod.ZodUUID;
+    }, zod.z.core.$strict>>>;
+}, zod.z.core.$strict>;
+export type StatusPageIncidentResource = zod.input<typeof StatusPageIncidentResource>;
+export type StatusPageIncidentResourceOutput = zod.output<typeof StatusPageIncidentResource>;

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

@@ -0,0 +1,37 @@
+/**
+ * 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 { StatusPageIncidentUpdateResource } from "./statusPageIncidentUpdateResource.zod.js";
+export const StatusPageIncidentResource = zod.strictObject({
+    impact: zod.enum(["NONE", "MINOR", "MAJOR", "CRITICAL"]),
+    incident_id: zod.uuid(),
+    incident_status: zod.enum(["INVESTIGATING", "IDENTIFIED", "MONITORING", "RESOLVED"]),
+    name: zod.string(),
+    published_at: zod.iso.datetime({ offset: true }),
+    resolved_at: zod.iso.datetime({ offset: true }).nullable(),
+    started_at: zod.iso
+        .datetime({ offset: true })
+        .describe("When the incident began, not when the notice was published"),
+    updates: zod
+        .array(StatusPageIncidentUpdateResource)
+        .nullable()
+        .describe("Most recently published first"),
+});

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

@@ -0,0 +1,52 @@
+/**
+ * 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 StatusPageIncidentUpdateResource: zod.ZodObject<{
+    affected_components: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        component_id: zod.ZodUUID;
+        component_name: zod.ZodString;
+        new_status: zod.ZodEnum<{
+            OPERATIONAL: "OPERATIONAL";
+            DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+            PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+            MAJOR_OUTAGE: "MAJOR_OUTAGE";
+            UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+        }>;
+        old_status: zod.ZodEnum<{
+            OPERATIONAL: "OPERATIONAL";
+            DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+            PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+            MAJOR_OUTAGE: "MAJOR_OUTAGE";
+            UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+        }>;
+    }, zod.z.core.$strict>>>;
+    body: zod.ZodString;
+    incident_status: zod.ZodEnum<{
+        RESOLVED: "RESOLVED";
+        INVESTIGATING: "INVESTIGATING";
+        IDENTIFIED: "IDENTIFIED";
+        MONITORING: "MONITORING";
+    }>;
+    published_at: zod.z.ZodISODateTime;
+    update_id: zod.ZodUUID;
+}, zod.z.core.$strict>;
+export type StatusPageIncidentUpdateResource = zod.input<typeof StatusPageIncidentUpdateResource>;
+export type StatusPageIncidentUpdateResourceOutput = zod.output<typeof StatusPageIncidentUpdateResource>;

package/dist/monitoring/v1/generated/validators/statusPageIncidentUpdateResource.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 { StatusPageIncidentComponentResource } from "./statusPageIncidentComponentResource.zod.js";
+export const StatusPageIncidentUpdateResource = zod.strictObject({
+    affected_components: zod.array(StatusPageIncidentComponentResource).nullable(),
+    body: zod.string().describe("Body text. Plain text"),
+    incident_status: zod.enum(["INVESTIGATING", "IDENTIFIED", "MONITORING", "RESOLVED"]),
+    published_at: zod.iso.datetime({ offset: true }),
+    update_id: zod.uuid(),
+});

package/dist/monitoring/v1/generated/validators/statusPageMaintenanceComponentRequest.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 statusPageMaintenanceComponentRequestComponentStatusDefault = "UNDER_MAINTENANCE";
+export declare const StatusPageMaintenanceComponentRequest: zod.ZodObject<{
+    component_id: zod.ZodUUID;
+    component_status: zod.ZodDefault<zod.ZodEnum<{
+        DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+        UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+    }>>;
+}, zod.z.core.$strict>;
+export type StatusPageMaintenanceComponentRequest = zod.input<typeof StatusPageMaintenanceComponentRequest>;
+export type StatusPageMaintenanceComponentRequestOutput = zod.output<typeof StatusPageMaintenanceComponentRequest>;

package/dist/monitoring/v1/generated/validators/statusPageMaintenanceComponentRequest.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 statusPageMaintenanceComponentRequestComponentStatusDefault = `UNDER_MAINTENANCE`;
+export const StatusPageMaintenanceComponentRequest = zod.strictObject({
+    component_id: zod.uuid(),
+    component_status: zod
+        .enum(["UNDER_MAINTENANCE", "DEGRADED_PERFORMANCE"])
+        .default(statusPageMaintenanceComponentRequestComponentStatusDefault)
+        .describe("How this component is shown while the maintenance runs. Neither value reduces availability"),
+});

package/dist/monitoring/v1/generated/validators/statusPageMaintenanceComponentResource.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 StatusPageMaintenanceComponentResource: zod.ZodObject<{
+    component_id: zod.ZodUUID;
+    component_name: zod.ZodString;
+    component_status: zod.ZodEnum<{
+        DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+        UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+    }>;
+}, zod.z.core.$strict>;
+export type StatusPageMaintenanceComponentResource = zod.input<typeof StatusPageMaintenanceComponentResource>;
+export type StatusPageMaintenanceComponentResourceOutput = zod.output<typeof StatusPageMaintenanceComponentResource>;

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

@@ -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 const StatusPageMaintenanceComponentResource = zod.strictObject({
+    component_id: zod.uuid(),
+    component_name: zod.string(),
+    component_status: zod.enum(["UNDER_MAINTENANCE", "DEGRADED_PERFORMANCE"]),
+});

package/dist/monitoring/v1/generated/validators/statusPageMaintenanceResource.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 StatusPageMaintenanceResource: zod.ZodObject<{
+    affected_components: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        component_id: zod.ZodUUID;
+        component_name: zod.ZodString;
+        component_status: zod.ZodEnum<{
+            DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+            UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+        }>;
+    }, zod.z.core.$strict>>>;
+    body: zod.ZodString;
+    completed_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    maintenance_id: zod.ZodUUID;
+    maintenance_status: zod.ZodEnum<{
+        SCHEDULED: "SCHEDULED";
+        IN_PROGRESS: "IN_PROGRESS";
+        COMPLETED: "COMPLETED";
+        CANCELLED: "CANCELLED";
+    }>;
+    name: zod.ZodString;
+    scheduled_for: zod.z.ZodISODateTime;
+    scheduled_until: zod.z.ZodISODateTime;
+    started_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+}, zod.z.core.$strict>;
+export type StatusPageMaintenanceResource = zod.input<typeof StatusPageMaintenanceResource>;
+export type StatusPageMaintenanceResourceOutput = zod.output<typeof StatusPageMaintenanceResource>;

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

@@ -0,0 +1,39 @@
+/**
+ * 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 { StatusPageMaintenanceComponentResource } from "./statusPageMaintenanceComponentResource.zod.js";
+export const StatusPageMaintenanceResource = zod.strictObject({
+    affected_components: zod.array(StatusPageMaintenanceComponentResource).nullable(),
+    body: zod.string().describe("Maintenance description. Plain text"),
+    completed_at: zod.iso
+        .datetime({ offset: true })
+        .nullable()
+        .describe("When the maintenance actually finished"),
+    maintenance_id: zod.uuid(),
+    maintenance_status: zod.enum(["SCHEDULED", "IN_PROGRESS", "COMPLETED", "CANCELLED"]),
+    name: zod.string(),
+    scheduled_for: zod.iso.datetime({ offset: true }),
+    scheduled_until: zod.iso.datetime({ offset: true }),
+    started_at: zod.iso
+        .datetime({ offset: true })
+        .nullable()
+        .describe("When the maintenance actually started, which may differ from the scheduled time"),
+});

package/dist/monitoring/v1/generated/validators/statusPageOrderItem.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 StatusPageOrderItem: zod.ZodObject<{
+    component_id: zod.ZodOptional<zod.ZodUUID>;
+    group_id: zod.ZodOptional<zod.ZodUUID>;
+}, zod.z.core.$strict>;
+export type StatusPageOrderItem = zod.input<typeof StatusPageOrderItem>;
+export type StatusPageOrderItemOutput = zod.output<typeof StatusPageOrderItem>;

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

@@ -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 const StatusPageOrderItem = zod
+    .strictObject({
+    component_id: zod.uuid().optional(),
+    group_id: zod.uuid().optional(),
+})
+    .describe("Exactly one of the two: `group_id` marks this position as a group, `component_id` as an ungrouped component");

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

@@ -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 declare const StatusPageResource: zod.ZodObject<{
+    brand_color: zod.ZodString;
+    created_at: zod.z.ZodISODateTime;
+    custom_domain: zod.ZodString;
+    footer_text: zod.ZodString;
+    headline: zod.ZodString;
+    logo_url: zod.ZodString;
+    name: zod.ZodString;
+    public_url: zod.ZodString;
+    published: zod.ZodBoolean;
+    search_engine_index: zod.ZodBoolean;
+    slug: zod.ZodString;
+    status_page_id: zod.ZodUUID;
+    support_url: zod.ZodString;
+    theme: zod.ZodEnum<{
+        AUTO: "AUTO";
+        LIGHT: "LIGHT";
+        DARK: "DARK";
+    }>;
+    timezone: zod.ZodString;
+    updated_at: zod.z.ZodISODateTime;
+    uptime_days: zod.ZodInt;
+    support_label: zod.ZodString;
+}, zod.z.core.$strict>;
+export type StatusPageResource = zod.input<typeof StatusPageResource>;
+export type StatusPageResourceOutput = zod.output<typeof StatusPageResource>;

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

@@ -0,0 +1,51 @@
+/**
+ * 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 StatusPageResource = zod.strictObject({
+    brand_color: zod.string().describe("#RRGGBB"),
+    created_at: zod.iso.datetime({ offset: true }),
+    custom_domain: zod
+        .string()
+        .describe("The custom domain bound to this page. Empty means it is served only at /{slug} under the shared domain"),
+    footer_text: zod.string(),
+    headline: zod.string(),
+    logo_url: zod.string(),
+    name: zod.string(),
+    public_url: zod
+        .string()
+        .describe("The address this page is served at: the custom domain if one is bound, otherwise the shared domain with the slug, otherwise the shared domain with the project id"),
+    published: zod.boolean(),
+    search_engine_index: zod.boolean().describe("Whether search engines may index the page"),
+    slug: zod
+        .string()
+        .describe("The readable address segment, empty when none is set. The page is always reachable at /<project id> regardless"),
+    status_page_id: zod.uuid(),
+    support_url: zod.string(),
+    theme: zod.enum(["AUTO", "LIGHT", "DARK"]),
+    timezone: zod
+        .string()
+        .describe("Determines where the day boundary falls on the availability bar"),
+    updated_at: zod.iso.datetime({ offset: true }),
+    uptime_days: zod.int().describe("Number of days covered by the availability bar"),
+    support_label: zod
+        .string()
+        .describe("The text shown on the support link. Empty means the page default is used"),
+});

package/dist/monitoring/v1/generated/validators/tagResource.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 TagResource: zod.ZodObject<{
+    tag: zod.ZodString;
+    value: zod.ZodString;
+}, zod.z.core.$strict>;
+export type TagResource = zod.input<typeof TagResource>;
+export type TagResourceOutput = zod.output<typeof TagResource>;

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

@@ -0,0 +1,25 @@
+/**
+ * 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 TagResource = zod.strictObject({
+    tag: zod.string(),
+    value: zod.string(),
+});

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

@@ -0,0 +1,39 @@
+/**
+ * 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 TemplateBindingRequest: zod.ZodObject<{
+    parameters: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
+    template_key: zod.ZodEnum<{
+        LINUX: "LINUX";
+        SYSTEMD: "SYSTEMD";
+        DOCKER: "DOCKER";
+        ICMP_PING: "ICMP_PING";
+        NGINX: "NGINX";
+        PHP_FPM: "PHP_FPM";
+        WEBSITE_CERTIFICATE: "WEBSITE_CERTIFICATE";
+        WINDOWS: "WINDOWS";
+        SMART: "SMART";
+        NVIDIA: "NVIDIA";
+        PROXMOX_VE: "PROXMOX_VE";
+    }>;
+}, zod.z.core.$strict>;
+export type TemplateBindingRequest = zod.input<typeof TemplateBindingRequest>;
+export type TemplateBindingRequestOutput = zod.output<typeof TemplateBindingRequest>;