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

package/dist/monitoring/v1/generated/validators/addCommentRequestBody.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 addCommentRequestBodyMessageMax = 2000;
+export declare const AddCommentRequestBody: zod.ZodObject<{
+    message: zod.ZodString;
+}, zod.z.core.$strict>;
+export type AddCommentRequestBody = zod.input<typeof AddCommentRequestBody>;
+export type AddCommentRequestBodyOutput = zod.output<typeof AddCommentRequestBody>;

package/dist/monitoring/v1/generated/validators/addCommentRequestBody.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 addCommentRequestBodyMessageMax = 2000;
+export const AddCommentRequestBody = zod.strictObject({
+    message: zod.string().min(1).max(addCommentRequestBodyMessageMax),
+});

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

@@ -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 declare const assignIncidentRequestBodyAssigneeDisplayNameMax = 255;
+export declare const assignIncidentRequestBodyAssigneeUserIdMax = 255;
+export declare const AssignIncidentRequestBody: zod.ZodObject<{
+    assignee_display_name: zod.ZodOptional<zod.ZodString>;
+    assignee_user_id: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type AssignIncidentRequestBody = zod.input<typeof AssignIncidentRequestBody>;
+export type AssignIncidentRequestBodyOutput = zod.output<typeof AssignIncidentRequestBody>;

package/dist/monitoring/v1/generated/validators/assignIncidentRequestBody.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";
+export const assignIncidentRequestBodyAssigneeDisplayNameMax = 255;
+export const assignIncidentRequestBodyAssigneeUserIdMax = 255;
+export const AssignIncidentRequestBody = zod.strictObject({
+    assignee_display_name: zod
+        .string()
+        .max(assignIncidentRequestBodyAssigneeDisplayNameMax)
+        .optional()
+        .describe("Defaults to the user id. The timeline keeps a copy of the name as it was at the time"),
+    assignee_user_id: zod.string().max(assignIncidentRequestBodyAssigneeUserIdMax).optional(),
+});

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

@@ -0,0 +1,36 @@
+/**
+ * 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 closeIncidentRequestBodyMessageMax = 2000;
+export declare const CloseIncidentRequestBody: zod.ZodObject<{
+    message: zod.ZodOptional<zod.ZodString>;
+    reason: zod.ZodEnum<{
+        RECOVERED: "RECOVERED";
+        FIXED: "FIXED";
+        FALSE_POSITIVE: "FALSE_POSITIVE";
+        DUPLICATE: "DUPLICATE";
+        NO_ACTION_REQUIRED: "NO_ACTION_REQUIRED";
+        ACCEPTED_RISK: "ACCEPTED_RISK";
+        OTHER: "OTHER";
+    }>;
+}, zod.z.core.$strict>;
+export type CloseIncidentRequestBody = zod.input<typeof CloseIncidentRequestBody>;
+export type CloseIncidentRequestBodyOutput = zod.output<typeof CloseIncidentRequestBody>;

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

@@ -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 const closeIncidentRequestBodyMessageMax = 2000;
+export const CloseIncidentRequestBody = zod.strictObject({
+    message: zod
+        .string()
+        .max(closeIncidentRequestBodyMessageMax)
+        .optional()
+        .describe("Required when `reason` is OTHER; the request is rejected otherwise"),
+    reason: zod.enum([
+        "RECOVERED",
+        "FIXED",
+        "FALSE_POSITIVE",
+        "DUPLICATE",
+        "NO_ACTION_REQUIRED",
+        "ACCEPTED_RISK",
+        "OTHER",
+    ]),
+});

package/dist/monitoring/v1/generated/validators/countResource.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 CountResource: zod.ZodObject<{
+    count: zod.ZodInt;
+    key: zod.ZodString;
+}, zod.z.core.$strict>;
+export type CountResource = zod.input<typeof CountResource>;
+export type CountResourceOutput = zod.output<typeof CountResource>;

package/dist/monitoring/v1/generated/validators/countResource.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 CountResource = zod.strictObject({
+    count: zod.int(),
+    key: zod.string(),
+});

package/dist/monitoring/v1/generated/validators/cursorPageIncidentActivityResource.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 CursorPageIncidentActivityResource: zod.ZodObject<{
+    items: zod.ZodArray<zod.ZodObject<{
+        activity_type: zod.ZodEnum<{
+            CLOSED: "CLOSED";
+            RECOVERED: "RECOVERED";
+            OPENED: "OPENED";
+            ACKNOWLEDGED: "ACKNOWLEDGED";
+            ASSIGNED: "ASSIGNED";
+            UNASSIGNED: "UNASSIGNED";
+            FOLLOWER_ADDED: "FOLLOWER_ADDED";
+            FOLLOWER_REMOVED: "FOLLOWER_REMOVED";
+            COMMENT: "COMMENT";
+            REOPENED: "REOPENED";
+        }>;
+        actor_display_name: zod.ZodString;
+        actor_user_id: zod.ZodString;
+        close_reason: zod.ZodString;
+        id: zod.ZodUUID;
+        incident_id: zod.ZodUUID;
+        message: zod.ZodString;
+        occurred_at: zod.z.ZodISODateTime;
+        source: zod.ZodEnum<{
+            SYSTEM: "SYSTEM";
+            OPERATOR: "OPERATOR";
+            ZABBIX: "ZABBIX";
+        }>;
+        subject_display_name: zod.ZodString;
+        subject_user_id: zod.ZodString;
+    }, zod.z.core.$strict>>;
+    next_cursor: zod.ZodString;
+}, zod.z.core.$strict>;
+export type CursorPageIncidentActivityResource = zod.input<typeof CursorPageIncidentActivityResource>;
+export type CursorPageIncidentActivityResourceOutput = zod.output<typeof CursorPageIncidentActivityResource>;

package/dist/monitoring/v1/generated/validators/cursorPageIncidentActivityResource.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";
+import { IncidentActivityResource } from "./incidentActivityResource.zod.js";
+export const CursorPageIncidentActivityResource = zod.strictObject({
+    items: zod.array(IncidentActivityResource).describe("The records in this page"),
+    next_cursor: zod
+        .string()
+        .describe("Cursor for the next page. Empty means the end has been reached"),
+});

package/dist/monitoring/v1/generated/validators/cursorPagination.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 CursorPagination: zod.ZodObject<{
+    page_size: zod.ZodInt;
+    next_cursor: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
+}, zod.z.core.$strict>;
+export type CursorPagination = zod.input<typeof CursorPagination>;
+export type CursorPaginationOutput = zod.output<typeof CursorPagination>;

package/dist/monitoring/v1/generated/validators/cursorPagination.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 CursorPagination = zod
+    .strictObject({
+    page_size: zod.int().min(1),
+    next_cursor: zod.string().nullish(),
+})
+    .describe("Pagination metadata for keyset traversal. Pass next_cursor as cursor to read the following page; null means there is no following page.");

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

@@ -0,0 +1,58 @@
+/**
+ * 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 enableMonitoringRequestBodyAddressMax = 255;
+export declare const enableMonitoringRequestBodyAgentPortMin = 0;
+export declare const enableMonitoringRequestBodyAgentPortMax = 65535;
+export declare const enableMonitoringRequestBodyDescriptionMax = 2000;
+export declare const enableMonitoringRequestBodyNameMax = 128;
+export declare const EnableMonitoringRequestBody: zod.ZodObject<{
+    address: zod.ZodString;
+    address_kind: zod.ZodEnum<{
+        ip: "ip";
+        dns: "dns";
+    }>;
+    agent_mode: zod.ZodOptional<zod.ZodEnum<{
+        ACTIVE: "ACTIVE";
+        PASSIVE: "PASSIVE";
+    }>>;
+    agent_port: zod.ZodOptional<zod.ZodInt>;
+    description: zod.ZodOptional<zod.ZodString>;
+    name: zod.ZodString;
+    template_bindings: zod.ZodOptional<zod.ZodNullable<zod.ZodArray<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>>>>;
+}, zod.z.core.$strict>;
+export type EnableMonitoringRequestBody = zod.input<typeof EnableMonitoringRequestBody>;
+export type EnableMonitoringRequestBodyOutput = zod.output<typeof EnableMonitoringRequestBody>;

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

@@ -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";
+import { TemplateBindingRequest } from "./templateBindingRequest.zod.js";
+export const enableMonitoringRequestBodyAddressMax = 255;
+export const enableMonitoringRequestBodyAgentPortMin = 0;
+export const enableMonitoringRequestBodyAgentPortMax = 65535;
+export const enableMonitoringRequestBodyDescriptionMax = 2000;
+export const enableMonitoringRequestBodyNameMax = 128;
+export const EnableMonitoringRequestBody = zod.strictObject({
+    address: zod.string().min(1).max(enableMonitoringRequestBodyAddressMax),
+    address_kind: zod.enum(["ip", "dns"]),
+    agent_mode: zod
+        .enum(["PASSIVE", "ACTIVE"])
+        .optional()
+        .describe("Empty selects passive mode, which requires the least agent-side configuration"),
+    agent_port: zod
+        .int()
+        .min(enableMonitoringRequestBodyAgentPortMin)
+        .max(enableMonitoringRequestBodyAgentPortMax)
+        .optional()
+        .describe("0 uses the default of 10050"),
+    description: zod.string().max(enableMonitoringRequestBodyDescriptionMax).optional(),
+    name: zod.string().min(1).max(enableMonitoringRequestBodyNameMax),
+    template_bindings: zod.array(TemplateBindingRequest).nullish(),
+});

package/dist/monitoring/v1/generated/validators/enrollmentResource.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 EnrollmentResource: 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>;
+export type EnrollmentResource = zod.input<typeof EnrollmentResource>;
+export type EnrollmentResourceOutput = zod.output<typeof EnrollmentResource>;

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

@@ -0,0 +1,33 @@
+/**
+ * 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 EnrollmentResource = zod.strictObject({
+    install_command: zod
+        .string()
+        .describe("Includes the PSK. Like `tls_psk`, it is returned only this once"),
+    install_script_url: zod.string(),
+    tls_psk: zod.string().describe("**Returned only this once**"),
+    tls_psk_identity: zod.string(),
+    zabbix_host_name: zod.string(),
+    zabbix_server_address: zod
+        .string()
+        .describe("The Server and ServerActive values for the agent configuration"),
+});

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

@@ -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 declare const Error: zod.ZodObject<{
+    code: zod.ZodOptional<zod.ZodString>;
+    message: zod.ZodString;
+    meta: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
+    status: zod.ZodInt;
+}, zod.z.core.$strict>;
+export type Error = zod.input<typeof Error>;
+export type ErrorOutput = zod.output<typeof Error>;

package/dist/monitoring/v1/generated/validators/error.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";
+export const Error = zod.strictObject({
+    code: zod.string().optional(),
+    message: zod.string(),
+    meta: zod
+        .record(zod.string(), zod.unknown())
+        .optional()
+        .describe("What a given `code` carries alongside the message. The keys depend on the code,\nand a client that does not recognise one ignores it."),
+    status: zod.int(),
+});