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

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

@@ -0,0 +1,43 @@
+/**
+ * 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 scheduleWindowRequestEndTimeSecondsMin = 0;
+export const scheduleWindowRequestEndTimeSecondsMax = 86400;
+export const scheduleWindowRequestStartTimeSecondsMin = 0;
+export const scheduleWindowRequestStartTimeSecondsMax = 86400;
+export const scheduleWindowRequestWeekdaysMax = 127;
+export const ScheduleWindowRequest = zod.strictObject({
+    end_time_seconds: zod
+        .int()
+        .min(scheduleWindowRequestEndTimeSecondsMin)
+        .max(scheduleWindowRequestEndTimeSecondsMax)
+        .optional(),
+    start_time_seconds: zod
+        .int()
+        .min(scheduleWindowRequestStartTimeSecondsMin)
+        .max(scheduleWindowRequestStartTimeSecondsMax)
+        .optional(),
+    weekdays: zod
+        .int()
+        .min(1)
+        .max(scheduleWindowRequestWeekdaysMax)
+        .describe("Bitmap of weekdays, **Monday is the lowest bit** (1 = Monday … 64 = Sunday)"),
+});

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

@@ -0,0 +1,28 @@
+/**
+ * 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 ScheduleWindowResource: zod.ZodObject<{
+    end_time_seconds: zod.ZodInt;
+    start_time_seconds: zod.ZodInt;
+    weekdays: zod.ZodInt;
+}, zod.z.core.$strict>;
+export type ScheduleWindowResource = zod.input<typeof ScheduleWindowResource>;
+export type ScheduleWindowResourceOutput = zod.output<typeof ScheduleWindowResource>;

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

@@ -0,0 +1,28 @@
+/**
+ * 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 ScheduleWindowResource = zod.strictObject({
+    end_time_seconds: zod.int(),
+    start_time_seconds: zod.int(),
+    weekdays: zod
+        .int()
+        .describe("Bitmap of weekdays, **Monday is the lowest bit**, using the same encoding as maintenance windows"),
+});

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

@@ -0,0 +1,66 @@
+/**
+ * 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 ServerEnrollmentResponseBody: zod.ZodObject<{
+    enrollment: zod.ZodObject<{
+        install_command: zod.ZodString;
+        install_script_url: zod.ZodString;
+        tls_psk: zod.ZodString;
+        tls_psk_identity: zod.ZodString;
+        zabbix_host_name: zod.ZodString;
+        zabbix_server_address: zod.ZodString;
+    }, zod.z.core.$strict>;
+    server: zod.ZodObject<{
+        address: zod.ZodString;
+        address_kind: zod.ZodEnum<{
+            ip: "ip";
+            dns: "dns";
+        }>;
+        agent_mode: zod.ZodEnum<{
+            ACTIVE: "ACTIVE";
+            PASSIVE: "PASSIVE";
+        }>;
+        agent_port: zod.ZodInt;
+        created_at: zod.z.ZodISODateTime;
+        description: zod.ZodString;
+        id: zod.ZodUUID;
+        last_error: zod.ZodString;
+        monitoring_status: zod.ZodEnum<{
+            ACTIVE: "ACTIVE";
+            PENDING: "PENDING";
+            FAILED: "FAILED";
+            DISABLED: "DISABLED";
+        }>;
+        name: zod.ZodString;
+        project_id: zod.ZodUUID;
+        templates: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+            configured_secret_parameters: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
+            parameters: zod.ZodRecord<zod.ZodString, zod.ZodString>;
+            template_key: zod.ZodString;
+            zabbix_template_id: zod.ZodString;
+            zabbix_template_name: zod.ZodString;
+        }, zod.z.core.$strict>>>;
+        updated_at: zod.z.ZodISODateTime;
+        zabbix_host_name: zod.ZodString;
+    }, zod.z.core.$strict>;
+}, zod.z.core.$strict>;
+export type ServerEnrollmentResponseBody = zod.input<typeof ServerEnrollmentResponseBody>;
+export type ServerEnrollmentResponseBodyOutput = zod.output<typeof ServerEnrollmentResponseBody>;

package/dist/monitoring/v1/generated/validators/serverEnrollmentResponseBody.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";
+import { EnrollmentResource } from "./enrollmentResource.zod.js";
+import { ServerResource } from "./serverResource.zod.js";
+export const ServerEnrollmentResponseBody = zod.strictObject({
+    enrollment: EnrollmentResource,
+    server: ServerResource,
+});

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

@@ -0,0 +1,56 @@
+/**
+ * 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 ServerResource: zod.ZodObject<{
+    address: zod.ZodString;
+    address_kind: zod.ZodEnum<{
+        ip: "ip";
+        dns: "dns";
+    }>;
+    agent_mode: zod.ZodEnum<{
+        ACTIVE: "ACTIVE";
+        PASSIVE: "PASSIVE";
+    }>;
+    agent_port: zod.ZodInt;
+    created_at: zod.z.ZodISODateTime;
+    description: zod.ZodString;
+    id: zod.ZodUUID;
+    last_error: zod.ZodString;
+    monitoring_status: zod.ZodEnum<{
+        ACTIVE: "ACTIVE";
+        PENDING: "PENDING";
+        FAILED: "FAILED";
+        DISABLED: "DISABLED";
+    }>;
+    name: zod.ZodString;
+    project_id: zod.ZodUUID;
+    templates: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        configured_secret_parameters: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
+        parameters: zod.ZodRecord<zod.ZodString, zod.ZodString>;
+        template_key: zod.ZodString;
+        zabbix_template_id: zod.ZodString;
+        zabbix_template_name: zod.ZodString;
+    }, zod.z.core.$strict>>>;
+    updated_at: zod.z.ZodISODateTime;
+    zabbix_host_name: zod.ZodString;
+}, zod.z.core.$strict>;
+export type ServerResource = zod.input<typeof ServerResource>;
+export type ServerResourceOutput = zod.output<typeof ServerResource>;

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

@@ -0,0 +1,42 @@
+/**
+ * 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 { ServerTemplateResource } from "./serverTemplateResource.zod.js";
+export const ServerResource = zod.strictObject({
+    address: zod.string(),
+    address_kind: zod.enum(["ip", "dns"]),
+    agent_mode: zod.enum(["PASSIVE", "ACTIVE"]),
+    agent_port: zod.int(),
+    created_at: zod.iso.datetime({ offset: true }),
+    description: zod.string(),
+    id: zod.uuid(),
+    last_error: zod.string(),
+    monitoring_status: zod
+        .enum(["PENDING", "ACTIVE", "DISABLED", "FAILED"])
+        .describe("Consult `last_error` when this is FAILED"),
+    name: zod.string(),
+    project_id: zod.uuid(),
+    templates: zod.array(ServerTemplateResource).nullable(),
+    updated_at: zod.iso.datetime({ offset: true }),
+    zabbix_host_name: zod
+        .string()
+        .describe("The Hostname in the agent configuration must match this value; active checks identify the machine by it"),
+});

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

@@ -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";
+export declare const ServerResourcesResource: zod.ZodObject<{
+    interfaces: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        available: zod.ZodBoolean;
+        dns: zod.ZodString;
+        ip: zod.ZodString;
+        port: zod.ZodInt;
+        use_ip: zod.ZodBoolean;
+    }, zod.z.core.$strict>>>;
+    inventory: zod.ZodRecord<zod.ZodString, zod.ZodString>;
+    tags: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        tag: zod.ZodString;
+        value: zod.ZodString;
+    }, zod.z.core.$strict>>>;
+}, zod.z.core.$strict>;
+export type ServerResourcesResource = zod.input<typeof ServerResourcesResource>;
+export type ServerResourcesResourceOutput = zod.output<typeof ServerResourcesResource>;

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

@@ -0,0 +1,30 @@
+/**
+ * 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 { HostInterfaceResource } from "./hostInterfaceResource.zod.js";
+import { TagResource } from "./tagResource.zod.js";
+export const ServerResourcesResource = zod.strictObject({
+    interfaces: zod.array(HostInterfaceResource).nullable(),
+    inventory: zod
+        .record(zod.string(), zod.string())
+        .describe("Hardware and system inventory collected automatically: CPU, memory, operating system and so on"),
+    tags: zod.array(TagResource).nullable(),
+});

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

@@ -0,0 +1,30 @@
+/**
+ * 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 ServerTemplateResource: zod.ZodObject<{
+    configured_secret_parameters: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
+    parameters: zod.ZodRecord<zod.ZodString, zod.ZodString>;
+    template_key: zod.ZodString;
+    zabbix_template_id: zod.ZodString;
+    zabbix_template_name: zod.ZodString;
+}, zod.z.core.$strict>;
+export type ServerTemplateResource = zod.input<typeof ServerTemplateResource>;
+export type ServerTemplateResourceOutput = zod.output<typeof ServerTemplateResource>;

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

@@ -0,0 +1,28 @@
+/**
+ * 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 ServerTemplateResource = zod.strictObject({
+    configured_secret_parameters: zod.array(zod.string()).nullable(),
+    parameters: zod.record(zod.string(), zod.string()),
+    template_key: zod.string(),
+    zabbix_template_id: zod.string(),
+    zabbix_template_name: zod.string(),
+});

package/dist/monitoring/v1/generated/validators/setFollowingRequestBody.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 SetFollowingRequestBody: zod.ZodObject<{
+    following: zod.ZodBoolean;
+}, zod.z.core.$strict>;
+export type SetFollowingRequestBody = zod.input<typeof SetFollowingRequestBody>;
+export type SetFollowingRequestBodyOutput = zod.output<typeof SetFollowingRequestBody>;

package/dist/monitoring/v1/generated/validators/setFollowingRequestBody.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 SetFollowingRequestBody = zod.strictObject({
+    following: zod.boolean(),
+});

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

@@ -0,0 +1,38 @@
+/**
+ * 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 SnapshotResource: zod.ZodObject<{
+    agent_error: zod.ZodString;
+    agent_reachability: zod.ZodEnum<{
+        UNKNOWN: "UNKNOWN";
+        REACHABLE: "REACHABLE";
+        AGENT_DOWN: "AGENT_DOWN";
+        UNREACHABLE: "UNREACHABLE";
+    }>;
+    last_collected_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    monitoring_enabled: zod.ZodBoolean;
+    problem_counts: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        count: zod.ZodInt;
+        key: zod.ZodString;
+    }, zod.z.core.$strict>>>;
+}, zod.z.core.$strict>;
+export type SnapshotResource = zod.input<typeof SnapshotResource>;
+export type SnapshotResourceOutput = zod.output<typeof SnapshotResource>;

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

@@ -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";
+import { CountResource } from "./countResource.zod.js";
+export const SnapshotResource = zod.strictObject({
+    agent_error: zod.string(),
+    agent_reachability: zod
+        .enum(["UNKNOWN", "REACHABLE", "AGENT_DOWN", "UNREACHABLE"])
+        .describe("AGENT_DOWN means the agent is unreachable while the machine is still alive; UNREACHABLE means neither can be established"),
+    last_collected_at: zod.iso.datetime({ offset: true }).nullable(),
+    monitoring_enabled: zod.boolean(),
+    problem_counts: zod.array(CountResource).nullable(),
+});

package/dist/monitoring/v1/generated/validators/statusPageComponentListResponseBody.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 StatusPageComponentListResponseBody: zod.ZodObject<{
+    data: zod.ZodArray<zod.ZodObject<{
+        auto_status_min_severity: zod.ZodEnum<{
+            INFORMATION: "INFORMATION";
+            WARNING: "WARNING";
+            AVERAGE: "AVERAGE";
+            HIGH: "HIGH";
+            DISASTER: "DISASTER";
+            ANY: "ANY";
+        }>;
+        component_id: zod.ZodUUID;
+        created_at: zod.z.ZodISODateTime;
+        current_status: zod.ZodEnum<{
+            OPERATIONAL: "OPERATIONAL";
+            DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+            PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+            MAJOR_OUTAGE: "MAJOR_OUTAGE";
+            UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+        }>;
+        description: zod.ZodString;
+        group_id: zod.ZodString;
+        name: zod.ZodString;
+        only_show_if_degraded: zod.ZodBoolean;
+        position: zod.ZodInt;
+        show_uptime: zod.ZodBoolean;
+        started_on: zod.z.ZodISODateTime;
+        uptime_percent: zod.ZodNumber;
+    }, zod.z.core.$strict>>;
+}, zod.z.core.$strict>;
+export type StatusPageComponentListResponseBody = zod.input<typeof StatusPageComponentListResponseBody>;
+export type StatusPageComponentListResponseBodyOutput = zod.output<typeof StatusPageComponentListResponseBody>;

package/dist/monitoring/v1/generated/validators/statusPageComponentListResponseBody.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";
+import { StatusPageComponentResource } from "./statusPageComponentResource.zod.js";
+export const StatusPageComponentListResponseBody = zod.strictObject({
+    data: zod.array(StatusPageComponentResource),
+});