@leaflow/sdk 0.0.0-dev.35.g30ba751 → 0.0.0-dev.353.g74313e0

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

@@ -0,0 +1,50 @@
+/**
+ * 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 StatusPageComponentResource: zod.ZodObject<{
+    auto_status_min_severity: zod.ZodEnum<{
+        INFORMATION: "INFORMATION";
+        WARNING: "WARNING";
+        AVERAGE: "AVERAGE";
+        HIGH: "HIGH";
+        DISASTER: "DISASTER";
+        ANY: "ANY";
+    }>;
+    component_id: zod.ZodUUID;
+    created_at: zod.z.ZodISODateTime;
+    current_status: zod.ZodEnum<{
+        OPERATIONAL: "OPERATIONAL";
+        DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+        PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+        MAJOR_OUTAGE: "MAJOR_OUTAGE";
+        UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+    }>;
+    description: zod.ZodString;
+    group_id: zod.ZodString;
+    name: zod.ZodString;
+    only_show_if_degraded: zod.ZodBoolean;
+    position: zod.ZodInt;
+    show_uptime: zod.ZodBoolean;
+    started_on: zod.z.ZodISODateTime;
+    uptime_percent: zod.ZodNumber;
+}, zod.z.core.$strict>;
+export type StatusPageComponentResource = zod.input<typeof StatusPageComponentResource>;
+export type StatusPageComponentResourceOutput = zod.output<typeof StatusPageComponentResource>;

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

@@ -0,0 +1,56 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const StatusPageComponentResource = zod.strictObject({
+    auto_status_min_severity: zod.enum([
+        "ANY",
+        "INFORMATION",
+        "WARNING",
+        "AVERAGE",
+        "HIGH",
+        "DISASTER",
+    ]),
+    component_id: zod.uuid(),
+    created_at: zod.iso.datetime({ offset: true }),
+    current_status: zod
+        .enum([
+        "OPERATIONAL",
+        "DEGRADED_PERFORMANCE",
+        "PARTIAL_OUTAGE",
+        "MAJOR_OUTAGE",
+        "UNDER_MAINTENANCE",
+    ])
+        .describe("The status currently shown to the public. OPERATIONAL means normal"),
+    description: zod.string(),
+    group_id: zod
+        .string()
+        .describe("Empty means ungrouped, placed directly at the top level of the page"),
+    name: zod.string(),
+    only_show_if_degraded: zod.boolean().describe("Hide this row while everything is normal"),
+    position: zod.int(),
+    show_uptime: zod
+        .boolean()
+        .describe("Whether the availability bar is shown. Components with this disabled are also excluded from the aggregate of their group"),
+    started_on: zod.iso
+        .datetime({ offset: true })
+        .describe("The moment this component started being covered. Earlier days are shown as unmeasured rather than operational"),
+    uptime_percent: zod.number().describe("Availability over the past `uptime_days` days"),
+});

package/dist/monitoring/v1/generated/validators/statusPageComponentSourceServer.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 StatusPageComponentSourceServer: zod.ZodObject<{
+    server_id: zod.ZodUUID;
+}, zod.z.core.$strict>;
+export type StatusPageComponentSourceServer = zod.input<typeof StatusPageComponentSourceServer>;
+export type StatusPageComponentSourceServerOutput = zod.output<typeof StatusPageComponentSourceServer>;

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

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

package/dist/monitoring/v1/generated/validators/statusPageComponentSourceWebCheck.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 statusPageComponentSourceWebCheckShowUrlDefault = false;
+export declare const StatusPageComponentSourceWebCheck: zod.ZodObject<{
+    show_url: zod.ZodDefault<zod.ZodBoolean>;
+    web_check_id: zod.ZodUUID;
+}, zod.z.core.$strict>;
+export type StatusPageComponentSourceWebCheck = zod.input<typeof StatusPageComponentSourceWebCheck>;
+export type StatusPageComponentSourceWebCheckOutput = zod.output<typeof StatusPageComponentSourceWebCheck>;

package/dist/monitoring/v1/generated/validators/statusPageComponentSourceWebCheck.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 statusPageComponentSourceWebCheckShowUrlDefault = false;
+export const StatusPageComponentSourceWebCheck = zod.strictObject({
+    show_url: zod
+        .boolean()
+        .default(statusPageComponentSourceWebCheckShowUrlDefault)
+        .describe("Whether the checked address is shown on the public page"),
+    web_check_id: zod.uuid(),
+});

package/dist/monitoring/v1/generated/validators/statusPageComponentSourcesResource.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 StatusPageComponentSourcesResource: zod.ZodObject<{
+    servers: zod.ZodArray<zod.ZodObject<{
+        server_id: zod.ZodUUID;
+    }, zod.z.core.$strict>>;
+    web_checks: zod.ZodArray<zod.ZodObject<{
+        show_url: zod.ZodDefault<zod.ZodBoolean>;
+        web_check_id: zod.ZodUUID;
+    }, zod.z.core.$strict>>;
+}, zod.z.core.$strict>;
+export type StatusPageComponentSourcesResource = zod.input<typeof StatusPageComponentSourcesResource>;
+export type StatusPageComponentSourcesResourceOutput = zod.output<typeof StatusPageComponentSourcesResource>;

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

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

package/dist/monitoring/v1/generated/validators/statusPageDomainResource.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 StatusPageDomainResource: zod.ZodObject<{
+    certificate_not_after: zod.ZodNullable<zod.z.ZodISODateTime>;
+    certificate_status: zod.ZodEnum<{
+        ACTIVE: "ACTIVE";
+        PENDING: "PENDING";
+        FAILED: "FAILED";
+        NONE: "NONE";
+    }>;
+    domain: zod.ZodString;
+    expected_cname: zod.ZodString;
+    last_error: zod.ZodString;
+    observed_cname: zod.ZodString;
+    public_url: zod.ZodString;
+    verified: zod.ZodBoolean;
+    verified_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+}, zod.z.core.$strict>;
+export type StatusPageDomainResource = zod.input<typeof StatusPageDomainResource>;
+export type StatusPageDomainResourceOutput = zod.output<typeof StatusPageDomainResource>;

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

@@ -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 const StatusPageDomainResource = zod.strictObject({
+    certificate_not_after: zod.iso
+        .datetime({ offset: true })
+        .nullable()
+        .describe("When the current certificate expires"),
+    certificate_status: zod
+        .enum(["NONE", "PENDING", "ACTIVE", "FAILED"])
+        .describe("NONE means no certificate has been requested for this domain yet"),
+    domain: zod.string().describe("The bound custom domain. Empty means none is bound"),
+    expected_cname: zod.string().describe("The value the domain must point at"),
+    last_error: zod
+        .string()
+        .describe("Why the most recent issuance attempt failed. Empty when it did not"),
+    observed_cname: zod
+        .string()
+        .describe("What the domain currently resolves to. Empty when it resolves to nothing"),
+    public_url: zod
+        .string()
+        .describe("The address this page is served at, taking the custom domain into account"),
+    verified: zod.boolean().describe("Whether the domain currently points at the status page"),
+    verified_at: zod.iso
+        .datetime({ offset: true })
+        .nullable()
+        .describe("When ownership was last confirmed"),
+});

package/dist/monitoring/v1/generated/validators/statusPageGroupListResponseBody.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 StatusPageGroupListResponseBody: zod.ZodObject<{
+    data: zod.ZodArray<zod.ZodObject<{
+        collapsed: zod.ZodBoolean;
+        created_at: zod.z.ZodISODateTime;
+        description: zod.ZodString;
+        group_id: zod.ZodUUID;
+        name: zod.ZodString;
+        position: zod.ZodInt;
+    }, zod.z.core.$strict>>;
+}, zod.z.core.$strict>;
+export type StatusPageGroupListResponseBody = zod.input<typeof StatusPageGroupListResponseBody>;
+export type StatusPageGroupListResponseBodyOutput = zod.output<typeof StatusPageGroupListResponseBody>;

package/dist/monitoring/v1/generated/validators/statusPageGroupListResponseBody.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 { StatusPageGroupResource } from "./statusPageGroupResource.zod.js";
+export const StatusPageGroupListResponseBody = zod.strictObject({
+    data: zod.array(StatusPageGroupResource),
+});

package/dist/monitoring/v1/generated/validators/statusPageGroupResource.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 StatusPageGroupResource: zod.ZodObject<{
+    collapsed: zod.ZodBoolean;
+    created_at: zod.z.ZodISODateTime;
+    description: zod.ZodString;
+    group_id: zod.ZodUUID;
+    name: zod.ZodString;
+    position: zod.ZodInt;
+}, zod.z.core.$strict>;
+export type StatusPageGroupResource = zod.input<typeof StatusPageGroupResource>;
+export type StatusPageGroupResourceOutput = zod.output<typeof StatusPageGroupResource>;

package/dist/monitoring/v1/generated/validators/statusPageGroupResource.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 StatusPageGroupResource = zod.strictObject({
+    collapsed: zod.boolean().describe("Whether the group is collapsed by default on the page"),
+    created_at: zod.iso.datetime({ offset: true }),
+    description: zod.string(),
+    group_id: zod.uuid(),
+    name: zod.string(),
+    position: zod.int(),
+});

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

package/dist/monitoring/v1/generated/validators/statusPageIncidentComponentRequest.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";
+export const StatusPageIncidentComponentRequest = zod.strictObject({
+    component_id: zod.uuid(),
+    status: zod
+        .enum([
+        "OPERATIONAL",
+        "DEGRADED_PERFORMANCE",
+        "PARTIAL_OUTAGE",
+        "MAJOR_OUTAGE",
+        "UNDER_MAINTENANCE",
+    ])
+        .optional()
+        .describe("Empty returns this component to operational"),
+});

package/dist/monitoring/v1/generated/validators/statusPageIncidentComponentResource.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 StatusPageIncidentComponentResource: zod.ZodObject<{
+    component_id: zod.ZodUUID;
+    component_name: zod.ZodString;
+    new_status: zod.ZodEnum<{
+        OPERATIONAL: "OPERATIONAL";
+        DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+        PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+        MAJOR_OUTAGE: "MAJOR_OUTAGE";
+        UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+    }>;
+    old_status: zod.ZodEnum<{
+        OPERATIONAL: "OPERATIONAL";
+        DEGRADED_PERFORMANCE: "DEGRADED_PERFORMANCE";
+        PARTIAL_OUTAGE: "PARTIAL_OUTAGE";
+        MAJOR_OUTAGE: "MAJOR_OUTAGE";
+        UNDER_MAINTENANCE: "UNDER_MAINTENANCE";
+    }>;
+}, zod.z.core.$strict>;
+export type StatusPageIncidentComponentResource = zod.input<typeof StatusPageIncidentComponentResource>;
+export type StatusPageIncidentComponentResourceOutput = zod.output<typeof StatusPageIncidentComponentResource>;

package/dist/monitoring/v1/generated/validators/statusPageIncidentComponentResource.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 StatusPageIncidentComponentResource = zod
+    .strictObject({
+    component_id: zod.uuid(),
+    component_name: zod.string(),
+    new_status: zod.enum([
+        "OPERATIONAL",
+        "DEGRADED_PERFORMANCE",
+        "PARTIAL_OUTAGE",
+        "MAJOR_OUTAGE",
+        "UNDER_MAINTENANCE",
+    ]),
+    old_status: zod.enum([
+        "OPERATIONAL",
+        "DEGRADED_PERFORMANCE",
+        "PARTIAL_OUTAGE",
+        "MAJOR_OUTAGE",
+        "UNDER_MAINTENANCE",
+    ]),
+})
+    .describe("A status transition of one component within one update. The component name is a snapshot taken at the time");