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

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

@@ -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 declare const listProjectTopItemsParamsLimitMin = 0;
+export declare const listProjectTopItemsParamsLimitMax = 100;
+export declare const ListProjectTopItemsParams: zod.ZodObject<{
+    kind: zod.ZodEnum<{
+        CPU_UTILIZATION: "CPU_UTILIZATION";
+        MEMORY_UTILIZATION: "MEMORY_UTILIZATION";
+        ROOT_FILESYSTEM_USED: "ROOT_FILESYSTEM_USED";
+    }>;
+    limit: zod.ZodOptional<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type ListProjectTopItemsParams = zod.input<typeof ListProjectTopItemsParams>;
+export type ListProjectTopItemsParamsOutput = zod.output<typeof ListProjectTopItemsParams>;

package/dist/monitoring/v1/generated/validators/listProjectTopItemsParams.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 listProjectTopItemsParamsLimitMin = 0;
+export const listProjectTopItemsParamsLimitMax = 100;
+export const ListProjectTopItemsParams = zod.strictObject({
+    kind: zod.enum(["CPU_UTILIZATION", "MEMORY_UTILIZATION", "ROOT_FILESYSTEM_USED"]),
+    limit: zod
+        .int()
+        .min(listProjectTopItemsParamsLimitMin)
+        .max(listProjectTopItemsParamsLimitMax)
+        .optional()
+        .describe("0 uses the default"),
+});

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

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

package/dist/monitoring/v1/generated/validators/listServerItemsParams.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 listServerItemsParamsKeywordMax = 255;
+export const ListServerItemsParams = zod.strictObject({
+    keyword: zod
+        .string()
+        .max(listServerItemsParamsKeywordMax)
+        .optional()
+        .describe("Fuzzy match on key or name"),
+    tag: zod
+        .array(zod.string())
+        .nullish()
+        .describe("Given as `key` or `key=value`, repeatable. The `component` tags applied by the official templates (cpu, memory, filesystem and so on) are filtered through this"),
+});

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

@@ -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 declare const listServersParamsLimitDefault = 50;
+export declare const listServersParamsLimitMax = 200;
+export declare const listServersParamsOffsetDefault = 0;
+export declare const listServersParamsOffsetMin = 0;
+export declare const listServersParamsOffsetMax = 10000;
+export declare const listServersParamsKeywordMax = 255;
+export declare const ListServersParams: zod.ZodObject<{
+    limit: zod.ZodDefault<zod.ZodInt>;
+    offset: zod.ZodDefault<zod.ZodInt>;
+    keyword: zod.ZodOptional<zod.ZodString>;
+    monitoring_status: zod.ZodOptional<zod.ZodEnum<{
+        ACTIVE: "ACTIVE";
+        PENDING: "PENDING";
+        FAILED: "FAILED";
+        DISABLED: "DISABLED";
+    }>>;
+}, zod.z.core.$strict>;
+export type ListServersParams = zod.input<typeof ListServersParams>;
+export type ListServersParamsOutput = zod.output<typeof ListServersParams>;

package/dist/monitoring/v1/generated/validators/listServersParams.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";
+export const listServersParamsLimitDefault = 50;
+export const listServersParamsLimitMax = 200;
+export const listServersParamsOffsetDefault = 0;
+export const listServersParamsOffsetMin = 0;
+export const listServersParamsOffsetMax = 10000;
+export const listServersParamsKeywordMax = 255;
+export const ListServersParams = zod.strictObject({
+    limit: zod.int().min(1).max(listServersParamsLimitMax).default(listServersParamsLimitDefault),
+    offset: zod
+        .int()
+        .min(listServersParamsOffsetMin)
+        .max(listServersParamsOffsetMax)
+        .default(listServersParamsOffsetDefault),
+    keyword: zod
+        .string()
+        .max(listServersParamsKeywordMax)
+        .optional()
+        .describe("Fuzzy match on name or address"),
+    monitoring_status: zod.enum(["PENDING", "ACTIVE", "DISABLED", "FAILED"]).optional(),
+});

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

@@ -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 declare const listStatusPageIncidentsParamsLimitDefault = 50;
+export declare const listStatusPageIncidentsParamsLimitMax = 200;
+export declare const listStatusPageIncidentsParamsOffsetDefault = 0;
+export declare const listStatusPageIncidentsParamsOffsetMin = 0;
+export declare const listStatusPageIncidentsParamsOffsetMax = 10000;
+export declare const ListStatusPageIncidentsParams: zod.ZodObject<{
+    limit: zod.ZodDefault<zod.ZodInt>;
+    offset: zod.ZodDefault<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type ListStatusPageIncidentsParams = zod.input<typeof ListStatusPageIncidentsParams>;
+export type ListStatusPageIncidentsParamsOutput = zod.output<typeof ListStatusPageIncidentsParams>;

package/dist/monitoring/v1/generated/validators/listStatusPageIncidentsParams.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 listStatusPageIncidentsParamsLimitDefault = 50;
+export const listStatusPageIncidentsParamsLimitMax = 200;
+export const listStatusPageIncidentsParamsOffsetDefault = 0;
+export const listStatusPageIncidentsParamsOffsetMin = 0;
+export const listStatusPageIncidentsParamsOffsetMax = 10000;
+export const ListStatusPageIncidentsParams = zod.strictObject({
+    limit: zod
+        .int()
+        .min(1)
+        .max(listStatusPageIncidentsParamsLimitMax)
+        .default(listStatusPageIncidentsParamsLimitDefault),
+    offset: zod
+        .int()
+        .min(listStatusPageIncidentsParamsOffsetMin)
+        .max(listStatusPageIncidentsParamsOffsetMax)
+        .default(listStatusPageIncidentsParamsOffsetDefault),
+});

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

@@ -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 declare const listStatusPageMaintenancesParamsLimitDefault = 50;
+export declare const listStatusPageMaintenancesParamsLimitMax = 200;
+export declare const listStatusPageMaintenancesParamsOffsetDefault = 0;
+export declare const listStatusPageMaintenancesParamsOffsetMin = 0;
+export declare const listStatusPageMaintenancesParamsOffsetMax = 10000;
+export declare const ListStatusPageMaintenancesParams: zod.ZodObject<{
+    limit: zod.ZodDefault<zod.ZodInt>;
+    offset: zod.ZodDefault<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type ListStatusPageMaintenancesParams = zod.input<typeof ListStatusPageMaintenancesParams>;
+export type ListStatusPageMaintenancesParamsOutput = zod.output<typeof ListStatusPageMaintenancesParams>;

package/dist/monitoring/v1/generated/validators/listStatusPageMaintenancesParams.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 listStatusPageMaintenancesParamsLimitDefault = 50;
+export const listStatusPageMaintenancesParamsLimitMax = 200;
+export const listStatusPageMaintenancesParamsOffsetDefault = 0;
+export const listStatusPageMaintenancesParamsOffsetMin = 0;
+export const listStatusPageMaintenancesParamsOffsetMax = 10000;
+export const ListStatusPageMaintenancesParams = zod.strictObject({
+    limit: zod
+        .int()
+        .min(1)
+        .max(listStatusPageMaintenancesParamsLimitMax)
+        .default(listStatusPageMaintenancesParamsLimitDefault),
+    offset: zod
+        .int()
+        .min(listStatusPageMaintenancesParamsOffsetMin)
+        .max(listStatusPageMaintenancesParamsOffsetMax)
+        .default(listStatusPageMaintenancesParamsOffsetDefault),
+});

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

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

package/dist/monitoring/v1/generated/validators/listWebChecksParams.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 ListWebChecksParams = zod.strictObject({
+    server_id: zod
+        .string()
+        .optional()
+        .describe("Restrict to the checks of a single machine. Omit for the whole project"),
+});

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

@@ -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";
+export declare const maintenancePeriodRequestDurationSecondsMin = 0;
+export declare const maintenancePeriodRequestEveryMin = 0;
+export declare const maintenancePeriodRequestStartTimeSecondsMin = 0;
+export declare const maintenancePeriodRequestStartTimeSecondsMax = 86399;
+export declare const maintenancePeriodRequestWeekdaysMin = 0;
+export declare const maintenancePeriodRequestWeekdaysMax = 127;
+export declare const MaintenancePeriodRequest: zod.ZodObject<{
+    duration_seconds: zod.ZodOptional<zod.ZodInt>;
+    every: zod.ZodOptional<zod.ZodInt>;
+    kind: zod.ZodEnum<{
+        ONCE: "ONCE";
+        DAILY: "DAILY";
+        WEEKLY: "WEEKLY";
+    }>;
+    start_time_seconds: zod.ZodOptional<zod.ZodInt>;
+    starts_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+    weekdays: zod.ZodOptional<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type MaintenancePeriodRequest = zod.input<typeof MaintenancePeriodRequest>;
+export type MaintenancePeriodRequestOutput = zod.output<typeof MaintenancePeriodRequest>;

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

@@ -0,0 +1,49 @@
+/**
+ * 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 maintenancePeriodRequestDurationSecondsMin = 0;
+export const maintenancePeriodRequestEveryMin = 0;
+export const maintenancePeriodRequestStartTimeSecondsMin = 0;
+export const maintenancePeriodRequestStartTimeSecondsMax = 86399;
+export const maintenancePeriodRequestWeekdaysMin = 0;
+export const maintenancePeriodRequestWeekdaysMax = 127;
+export const MaintenancePeriodRequest = zod.strictObject({
+    duration_seconds: zod.int().min(maintenancePeriodRequestDurationSecondsMin).optional(),
+    every: zod
+        .int()
+        .min(maintenancePeriodRequestEveryMin)
+        .optional()
+        .describe("DAILY and WEEKLY: every N days or every N weeks"),
+    kind: zod.enum(["ONCE", "DAILY", "WEEKLY"]),
+    start_time_seconds: zod
+        .int()
+        .min(maintenancePeriodRequestStartTimeSecondsMin)
+        .max(maintenancePeriodRequestStartTimeSecondsMax)
+        .optional()
+        .describe("DAILY and WEEKLY: seconds from midnight, in the timezone of the window"),
+    starts_at: zod.iso.datetime({ offset: true }).optional().describe("Used only by ONCE"),
+    weekdays: zod
+        .int()
+        .min(maintenancePeriodRequestWeekdaysMin)
+        .max(maintenancePeriodRequestWeekdaysMax)
+        .optional()
+        .describe("WEEKLY: bitmap of weekdays, **Monday is the lowest bit**"),
+});

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

package/dist/monitoring/v1/generated/validators/maintenancePeriodResource.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 MaintenancePeriodResource = zod.strictObject({
+    duration_seconds: zod.int(),
+    every: zod.int().describe("DAILY and WEEKLY: every N days or every N weeks"),
+    kind: zod.enum(["ONCE", "DAILY", "WEEKLY"]),
+    start_time_seconds: zod
+        .int()
+        .describe("DAILY and WEEKLY: seconds from midnight, in the timezone of the window"),
+    starts_at: zod.iso.datetime({ offset: true }).nullable().describe("Present only for ONCE"),
+    weekdays: zod.int().describe("WEEKLY: bitmap of weekdays, **Monday is the lowest bit**"),
+});

package/dist/monitoring/v1/generated/validators/maintenanceWindowListResponseBody.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 MaintenanceWindowListResponseBody: zod.ZodObject<{
+    items: zod.ZodNullable<zod.ZodArray<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>>>;
+}, zod.z.core.$strict>;
+export type MaintenanceWindowListResponseBody = zod.input<typeof MaintenanceWindowListResponseBody>;
+export type MaintenanceWindowListResponseBodyOutput = zod.output<typeof MaintenanceWindowListResponseBody>;