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

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

@@ -0,0 +1,40 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const TemplateBindingRequest = zod.strictObject({
+    parameters: zod
+        .record(zod.string(), zod.string())
+        .optional()
+        .describe("Parameters declared by the template, keyed by `name` from `GET /templates`. This is a full replacement: a parameter that is omitted takes the `default` reported there, so send back the whole `parameters` map read from the machine rather than only the field being changed.\n\nSecret parameters are the one exception, because they are never returned and so cannot be sent back. Omit one to keep the value already stored, and supply it only to replace it. An empty or blank value counts as omitted."),
+    template_key: zod.enum([
+        "LINUX",
+        "SYSTEMD",
+        "DOCKER",
+        "ICMP_PING",
+        "NGINX",
+        "PHP_FPM",
+        "WEBSITE_CERTIFICATE",
+        "WINDOWS",
+        "SMART",
+        "NVIDIA",
+        "PROXMOX_VE",
+    ]),
+});

package/dist/monitoring/v1/generated/validators/templateCatalogEntryResource.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 TemplateCatalogEntryResource: zod.ZodObject<{
+    is_base: zod.ZodBoolean;
+    needs_agent: zod.ZodBoolean;
+    parameters: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        default: zod.ZodString;
+        kind: zod.ZodEnum<{
+            string: "string";
+            non_empty_string: "non_empty_string";
+            percent: "percent";
+            positive_number: "positive_number";
+            port: "port";
+            host: "host";
+            ip_or_empty: "ip_or_empty";
+            regexp: "regexp";
+        }>;
+        name: zod.ZodString;
+        required: zod.ZodBoolean;
+        secret: zod.ZodBoolean;
+    }, zod.z.core.$strict>>>;
+    requires: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
+    supports_active_mode: zod.ZodBoolean;
+    template_key: zod.ZodString;
+}, zod.z.core.$strict>;
+export type TemplateCatalogEntryResource = zod.input<typeof TemplateCatalogEntryResource>;
+export type TemplateCatalogEntryResourceOutput = zod.output<typeof TemplateCatalogEntryResource>;

package/dist/monitoring/v1/generated/validators/templateCatalogEntryResource.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 { TemplateCatalogParameterResource } from "./templateCatalogParameterResource.zod.js";
+export const TemplateCatalogEntryResource = zod.strictObject({
+    is_base: zod
+        .boolean()
+        .describe("Exactly one template with this set must be bound to every machine. Binding none enrolls a machine that can never alert; binding both loads the Linux and Windows items onto one machine, half of which must fail"),
+    needs_agent: zod
+        .boolean()
+        .describe("False means the template collects without an agent on the machine — ICMP_PING is pinged by the Zabbix server, PROXMOX_VE is polled over the PVE API"),
+    parameters: zod
+        .array(TemplateCatalogParameterResource)
+        .nullable()
+        .describe("In declaration order — connection parameters first, thresholds after — and meant to be rendered in that order. It is deliberately not alphabetical, which would split a template's connection parameters apart with thresholds between them even though they only make sense filled in together"),
+    requires: zod
+        .array(zod.string())
+        .nullable()
+        .describe("Templates that must be bound alongside this one. Values are `template_key`s"),
+    supports_active_mode: zod
+        .boolean()
+        .describe("Whether this template may be bound when `agent_mode` is ACTIVE. It already combines both reasons it may not be — no active variant exists, or this deployment does not have one installed — because the two are rejected identically and call for the same fix"),
+    template_key: zod.string(),
+});

package/dist/monitoring/v1/generated/validators/templateCatalogParameterResource.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 TemplateCatalogParameterResource: zod.ZodObject<{
+    default: zod.ZodString;
+    kind: zod.ZodEnum<{
+        string: "string";
+        non_empty_string: "non_empty_string";
+        percent: "percent";
+        positive_number: "positive_number";
+        port: "port";
+        host: "host";
+        ip_or_empty: "ip_or_empty";
+        regexp: "regexp";
+    }>;
+    name: zod.ZodString;
+    required: zod.ZodBoolean;
+    secret: zod.ZodBoolean;
+}, zod.z.core.$strict>;
+export type TemplateCatalogParameterResource = zod.input<typeof TemplateCatalogParameterResource>;
+export type TemplateCatalogParameterResourceOutput = zod.output<typeof TemplateCatalogParameterResource>;

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

@@ -0,0 +1,47 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const TemplateCatalogParameterResource = zod.strictObject({
+    default: zod
+        .string()
+        .describe("The value that takes effect when the parameter is omitted. An empty string is a real default, not an absent one"),
+    kind: zod
+        .enum([
+        "string",
+        "non_empty_string",
+        "percent",
+        "positive_number",
+        "port",
+        "host",
+        "ip_or_empty",
+        "regexp",
+    ])
+        .describe('The shape of the accepted value. Surrounding whitespace is trimmed before the value is checked, and an omitted or empty value is replaced by `default` and not checked at all.\n\n- `string` — no constraint; empty is accepted\n- `non_empty_string` — must not be empty once trimmed\n- `percent` — a number in the **closed** interval 0 to 100; fractions are accepted\n- `positive_number` — a number **strictly** greater than 0; fractions are accepted\n- `port` — an integer from 1 to 65535 inclusive; `8080/tcp` is not a port\n- `host` — an IP address, or a hostname of at most 255 characters whose dot-separated labels are at most 63 characters of `A-Z a-z 0-9 - _` and neither begin nor end with `-`. A single label such as `localhost` is accepted, as is a trailing dot\n- `ip_or_empty` — an IP address, or empty to mean "not specified"\n- `regexp` — must compile as a **Go RE2** pattern. RE2 has no backreferences and no lookaround, so a pattern that a browser\'s `new RegExp()` accepts may still be rejected here. Validating client-side narrows the gap but does not close it'),
+    name: zod
+        .string()
+        .describe("The key to use in `template_bindings[].parameters`. It is not the Zabbix macro name, which is internal and changes between Zabbix versions"),
+    required: zod
+        .boolean()
+        .describe("Independent of `default`. The three NGINX connection parameters carry a default and are still required, because the template's own default (localhost:80/basic_status) is almost never right"),
+    secret: zod
+        .boolean()
+        .describe("Supplied in clear text and never returned. A configured one is reported by name only, through `configured_secret_parameters` on the bound template. When updating a machine that already has one stored, omit it to keep the stored value and supply it only to replace it — a caller cannot read it back, so requiring it on every write would make resuming collection impossible"),
+});

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

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

package/dist/monitoring/v1/generated/validators/templateCatalogResponseBody.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 { TemplateCatalogEntryResource } from "./templateCatalogEntryResource.zod.js";
+export const TemplateCatalogResponseBody = zod.strictObject({
+    items: zod.array(TemplateCatalogEntryResource).nullable(),
+});

package/dist/monitoring/v1/generated/validators/topItemListResponseBody.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 TopItemListResponseBody: zod.ZodObject<{
+    items: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        item_key: zod.ZodString;
+        server_id: zod.ZodUUID;
+        units: zod.ZodString;
+        value: zod.ZodNumber;
+    }, zod.z.core.$strict>>>;
+}, zod.z.core.$strict>;
+export type TopItemListResponseBody = zod.input<typeof TopItemListResponseBody>;
+export type TopItemListResponseBodyOutput = zod.output<typeof TopItemListResponseBody>;

package/dist/monitoring/v1/generated/validators/topItemListResponseBody.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 { TopItemResource } from "./topItemResource.zod.js";
+export const TopItemListResponseBody = zod.strictObject({
+    items: zod.array(TopItemResource).nullable(),
+});

package/dist/monitoring/v1/generated/validators/topItemResource.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 TopItemResource: zod.ZodObject<{
+    item_key: zod.ZodString;
+    server_id: zod.ZodUUID;
+    units: zod.ZodString;
+    value: zod.ZodNumber;
+}, zod.z.core.$strict>;
+export type TopItemResource = zod.input<typeof TopItemResource>;
+export type TopItemResourceOutput = zod.output<typeof TopItemResource>;

package/dist/monitoring/v1/generated/validators/topItemResource.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 TopItemResource = zod.strictObject({
+    item_key: zod.string(),
+    server_id: zod.uuid(),
+    units: zod.string(),
+    value: zod.number(),
+});

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

@@ -0,0 +1,57 @@
+/**
+ * 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 updateServerRequestBodyAddressMax = 255;
+export declare const updateServerRequestBodyAgentPortMax = 65535;
+export declare const updateServerRequestBodyDescriptionMax = 2000;
+export declare const updateServerRequestBodyNameMax = 128;
+export declare const UpdateServerRequestBody: zod.ZodObject<{
+    address: zod.ZodOptional<zod.ZodString>;
+    address_kind: zod.ZodOptional<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.ZodOptional<zod.ZodString>;
+    template_bindings: zod.ZodOptional<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 UpdateServerRequestBody = zod.input<typeof UpdateServerRequestBody>;
+export type UpdateServerRequestBodyOutput = zod.output<typeof UpdateServerRequestBody>;

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

@@ -0,0 +1,41 @@
+/**
+ * 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 updateServerRequestBodyAddressMax = 255;
+export const updateServerRequestBodyAgentPortMax = 65535;
+export const updateServerRequestBodyDescriptionMax = 2000;
+export const updateServerRequestBodyNameMax = 128;
+export const UpdateServerRequestBody = zod.strictObject({
+    address: zod.string().max(updateServerRequestBodyAddressMax).optional(),
+    address_kind: zod
+        .enum(["ip", "dns"])
+        .optional()
+        .describe("Must be supplied together with `address` when changing the address"),
+    agent_mode: zod
+        .enum(["PASSIVE", "ACTIVE"])
+        .optional()
+        .describe("Changing the collection mode rebinds every template to the corresponding variant"),
+    agent_port: zod.int().min(1).max(updateServerRequestBodyAgentPortMax).optional(),
+    description: zod.string().max(updateServerRequestBodyDescriptionMax).optional(),
+    name: zod.string().min(1).max(updateServerRequestBodyNameMax).optional(),
+    template_bindings: zod.array(TemplateBindingRequest).optional(),
+});

package/dist/monitoring/v1/generated/validators/webCheckListResponseBody.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 WebCheckListResponseBody: zod.ZodObject<{
+    items: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        check_id: zod.ZodUUID;
+        interval_seconds: zod.ZodInt;
+        last_error: zod.ZodString;
+        response_time_threshold_seconds: zod.ZodInt;
+        result: zod.ZodUnion<readonly [zod.ZodObject<{
+            checked_at: zod.z.ZodISODateTime;
+            error: zod.ZodString;
+            failed_step: zod.ZodInt;
+            healthy: zod.ZodBoolean;
+            response_code: zod.ZodInt;
+            response_time_seconds: zod.ZodNumber;
+        }, zod.z.core.$strict>, zod.ZodNull]>;
+        retries: zod.ZodInt;
+        server_id: zod.ZodUUID;
+        steps: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+            expected_status_codes: zod.ZodString;
+            follow_redirects: zod.ZodBoolean;
+            name: zod.ZodString;
+            required_pattern: zod.ZodString;
+            url: zod.ZodString;
+        }, zod.z.core.$strict>>>;
+        sync_status: zod.ZodEnum<{
+            ACTIVE: "ACTIVE";
+            PENDING: "PENDING";
+            FAILED: "FAILED";
+        }>;
+        timeout_seconds: zod.ZodInt;
+    }, zod.z.core.$strict>>>;
+}, zod.z.core.$strict>;
+export type WebCheckListResponseBody = zod.input<typeof WebCheckListResponseBody>;
+export type WebCheckListResponseBodyOutput = zod.output<typeof WebCheckListResponseBody>;

package/dist/monitoring/v1/generated/validators/webCheckListResponseBody.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 { WebCheckResource } from "./webCheckResource.zod.js";
+export const WebCheckListResponseBody = zod.strictObject({
+    items: zod.array(WebCheckResource).nullable(),
+});

package/dist/monitoring/v1/generated/validators/webCheckResource.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 WebCheckResource: zod.ZodObject<{
+    check_id: zod.ZodUUID;
+    interval_seconds: zod.ZodInt;
+    last_error: zod.ZodString;
+    response_time_threshold_seconds: zod.ZodInt;
+    result: zod.ZodUnion<readonly [zod.ZodObject<{
+        checked_at: zod.z.ZodISODateTime;
+        error: zod.ZodString;
+        failed_step: zod.ZodInt;
+        healthy: zod.ZodBoolean;
+        response_code: zod.ZodInt;
+        response_time_seconds: zod.ZodNumber;
+    }, zod.z.core.$strict>, zod.ZodNull]>;
+    retries: zod.ZodInt;
+    server_id: zod.ZodUUID;
+    steps: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        expected_status_codes: zod.ZodString;
+        follow_redirects: zod.ZodBoolean;
+        name: zod.ZodString;
+        required_pattern: zod.ZodString;
+        url: zod.ZodString;
+    }, zod.z.core.$strict>>>;
+    sync_status: zod.ZodEnum<{
+        ACTIVE: "ACTIVE";
+        PENDING: "PENDING";
+        FAILED: "FAILED";
+    }>;
+    timeout_seconds: zod.ZodInt;
+}, zod.z.core.$strict>;
+export type WebCheckResource = zod.input<typeof WebCheckResource>;
+export type WebCheckResourceOutput = zod.output<typeof WebCheckResource>;