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

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

package/dist/monitoring/v1/generated/validators/maintenanceWindowResource.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 MaintenanceWindowResource: zod.ZodObject<{
+    active_since: zod.z.ZodISODateTime;
+    active_till: zod.z.ZodISODateTime;
+    description: zod.ZodString;
+    last_error: zod.ZodString;
+    name: zod.ZodString;
+    period: zod.ZodObject<{
+        duration_seconds: zod.ZodInt;
+        every: zod.ZodInt;
+        kind: zod.ZodEnum<{
+            ONCE: "ONCE";
+            DAILY: "DAILY";
+            WEEKLY: "WEEKLY";
+        }>;
+        start_time_seconds: zod.ZodInt;
+        starts_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+        weekdays: zod.ZodInt;
+    }, zod.z.core.$strict>;
+    project_id: zod.ZodUUID;
+    server_ids: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
+    sync_status: zod.ZodEnum<{
+        ACTIVE: "ACTIVE";
+        PENDING: "PENDING";
+        FAILED: "FAILED";
+        EXPIRED: "EXPIRED";
+    }>;
+    timezone: zod.ZodString;
+    window_id: zod.ZodUUID;
+}, zod.z.core.$strict>;
+export type MaintenanceWindowResource = zod.input<typeof MaintenanceWindowResource>;
+export type MaintenanceWindowResourceOutput = zod.output<typeof MaintenanceWindowResource>;

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

@@ -0,0 +1,35 @@
+/**
+ * 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 { MaintenancePeriodResource } from "./maintenancePeriodResource.zod.js";
+export const MaintenanceWindowResource = zod.strictObject({
+    active_since: zod.iso.datetime({ offset: true }),
+    active_till: zod.iso.datetime({ offset: true }),
+    description: zod.string(),
+    last_error: zod.string(),
+    name: zod.string(),
+    period: MaintenancePeriodResource,
+    project_id: zod.uuid(),
+    server_ids: zod.array(zod.string()).nullable().describe("Empty covers the **entire project**"),
+    sync_status: zod.enum(["PENDING", "ACTIVE", "FAILED", "EXPIRED"]),
+    timezone: zod.string(),
+    window_id: zod.uuid(),
+});

package/dist/monitoring/v1/generated/validators/metricPointResource.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 MetricPointResource: zod.ZodObject<{
+    max_value: zod.ZodNumber;
+    min_value: zod.ZodNumber;
+    timestamp: zod.z.ZodISODateTime;
+    value: zod.ZodNumber;
+}, zod.z.core.$strict>;
+export type MetricPointResource = zod.input<typeof MetricPointResource>;
+export type MetricPointResourceOutput = zod.output<typeof MetricPointResource>;

package/dist/monitoring/v1/generated/validators/metricPointResource.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 MetricPointResource = zod.strictObject({
+    max_value: zod.number(),
+    min_value: zod.number(),
+    timestamp: zod.iso.datetime({ offset: true }),
+    value: zod.number(),
+});

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

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

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

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

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

@@ -0,0 +1,35 @@
+/**
+ * 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 MetricSeriesResource: zod.ZodObject<{
+    item_id: zod.ZodString;
+    item_key: zod.ZodString;
+    item_name: zod.ZodString;
+    points: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        max_value: zod.ZodNumber;
+        min_value: zod.ZodNumber;
+        timestamp: zod.z.ZodISODateTime;
+        value: zod.ZodNumber;
+    }, zod.z.core.$strict>>>;
+    units: zod.ZodString;
+}, zod.z.core.$strict>;
+export type MetricSeriesResource = zod.input<typeof MetricSeriesResource>;
+export type MetricSeriesResourceOutput = zod.output<typeof MetricSeriesResource>;

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

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

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

@@ -0,0 +1,34 @@
+/**
+ * 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 MonitoringItemResource: zod.ZodObject<{
+    aggregation_function: zod.ZodString;
+    evaluation_window_seconds: zod.ZodInt;
+    item_id: zod.ZodString;
+    key: zod.ZodString;
+    name: zod.ZodString;
+    operator: zod.ZodString;
+    threshold: zod.ZodNullable<zod.ZodNumber>;
+    threshold_status: zod.ZodString;
+    value: zod.ZodString;
+}, zod.z.core.$strict>;
+export type MonitoringItemResource = zod.input<typeof MonitoringItemResource>;
+export type MonitoringItemResourceOutput = zod.output<typeof MonitoringItemResource>;

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

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

package/dist/monitoring/v1/generated/validators/offsetPagination.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 offsetPaginationTotalCountMin = 0;
+export declare const OffsetPagination: zod.ZodObject<{
+    page: zod.ZodInt;
+    page_size: zod.ZodInt;
+    total_count: zod.ZodOptional<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type OffsetPagination = zod.input<typeof OffsetPagination>;
+export type OffsetPaginationOutput = zod.output<typeof OffsetPagination>;

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

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

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

@@ -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 declare const PostStatusPageIncidentUpdateRequestBody: zod.ZodObject<{
+    body: zod.ZodString;
+    components: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
+        component_id: zod.ZodUUID;
+        status: zod.ZodOptional<zod.ZodEnum<{
+            OPERATIONAL: "OPERATIONAL";
+            DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+            PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+            MAJOR_OUTAGE: "MAJOR_OUTAGE";
+            UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+        }>>;
+    }, zod.z.core.$strict>>>;
+    incident_status: zod.ZodOptional<zod.ZodEnum<{
+        RESOLVED: "RESOLVED";
+        INVESTIGATING: "INVESTIGATING";
+        IDENTIFIED: "IDENTIFIED";
+        MONITORING: "MONITORING";
+    }>>;
+    published_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+}, zod.z.core.$strict>;
+export type PostStatusPageIncidentUpdateRequestBody = zod.input<typeof PostStatusPageIncidentUpdateRequestBody>;
+export type PostStatusPageIncidentUpdateRequestBodyOutput = zod.output<typeof PostStatusPageIncidentUpdateRequestBody>;

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

@@ -0,0 +1,34 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { StatusPageIncidentComponentRequest } from "./statusPageIncidentComponentRequest.zod.js";
+export const PostStatusPageIncidentUpdateRequestBody = zod.strictObject({
+    body: zod.string().min(1).describe("Body text. Plain text"),
+    components: zod
+        .array(StatusPageIncidentComponentRequest)
+        .optional()
+        .describe("Lists only the components being changed by this update; those not listed keep their current status"),
+    incident_status: zod
+        .enum(["INVESTIGATING", "IDENTIFIED", "MONITORING", "RESOLVED"])
+        .optional()
+        .describe("Empty keeps the current stage. RESOLVED closes the notice and returns every affected component to operational"),
+    published_at: zod.iso.datetime({ offset: true }).optional(),
+});

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

@@ -0,0 +1,35 @@
+/**
+ * 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 ProjectOverviewResource: zod.ZodObject<{
+    monitored_servers: zod.ZodInt;
+    problem_counts: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        count: zod.ZodInt;
+        key: zod.ZodString;
+    }, zod.z.core.$strict>>>;
+    reachability_counts: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        count: zod.ZodInt;
+        key: zod.ZodString;
+    }, zod.z.core.$strict>>>;
+    total_servers: zod.ZodInt;
+}, zod.z.core.$strict>;
+export type ProjectOverviewResource = zod.input<typeof ProjectOverviewResource>;
+export type ProjectOverviewResourceOutput = zod.output<typeof ProjectOverviewResource>;

package/dist/monitoring/v1/generated/validators/projectOverviewResource.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 { CountResource } from "./countResource.zod.js";
+export const ProjectOverviewResource = zod.strictObject({
+    monitored_servers: zod.int(),
+    problem_counts: zod.array(CountResource).nullable(),
+    reachability_counts: zod.array(CountResource).nullable(),
+    total_servers: zod.int(),
+});