@homeflare/distilled-proxmox 0.2.0 → 0.3.1

package/dist/services/nodes.d.ts

@@ -2,6 +2,26 @@ import * as S from "@distilled.cloud/core/schema";
 import * as API from "@distilled.cloud/core/api";
 import { type ProxmoxOpError, type ProxmoxOpContext } from "../protocol.ts";
 export type { ProxmoxOpError, ProxmoxOpContext };
+declare const CephFsNotFound_base: S.Class<CephFsNotFound, S.TaggedStruct<"CephFsNotFound", {
+    readonly message: any;
+}>, import("effect/Cause").YieldableError> & (new (...args: any[]) => {
+    "@distilled.cloud/error/categories": {
+        BadRequestError: true;
+    };
+});
+/** The Ceph filesystem does not exist. PVE's `destroyfs` dies synchronously with `no such cephfs '<name>'` when the named filesystem is already gone (an async task is never even queued, so this surfaces directly from the DELETE call, not from polling its UPID). This shape states the honest status (404) while matching the wire's real one — 500, the same class PVE answers for a missing user/group/storage/pool. Traced to source, not paraphrased (correcting an earlier draft of this patch, which carried forward the kit's own paraphrase, 'no such cephfs' with no filesystem name — the kit comments it cited, `ceph-fs-wire.ts:203-206` and `ceph-fs.ts:230-233`, never claimed to quote the wire text verbatim either): `pve-manager` (commit f6997e698c7933ea8e62319e2bf1bf7262daa56a, "bump version to 9.2.11") `PVE/API2/Ceph/FS.pm:327`, inside the `DELETE .../ceph/fs/{name}` handler's `code => sub`: `die "no such cephfs '$fs_name'\n" if !$fs;` — reached only when `$fs_name` (the `name` path label) is not found in `PVE::Ceph::Tools::ls_fs()`'s list. No live DELETE was run to confirm this byte-for-byte (per this pass's read-only-GET constraint); the regex is anchored on the verified-from-source prefix and object-kind qualifier only, deliberately not asserting the exact trailing punctuation/newline. */
+export declare class CephFsNotFound extends /*@__PURE__*/ CephFsNotFound_base {
+}
+declare const CephPoolNotFound_base: S.Class<CephPoolNotFound, S.TaggedStruct<"CephPoolNotFound", {
+    readonly message: any;
+}>, import("effect/Cause").YieldableError> & (new (...args: any[]) => {
+    "@distilled.cloud/error/categories": {
+        BadRequestError: true;
+    };
+});
+/** The Ceph pool does not exist. PVE shells out to `ceph osd pool get` and reports its failure verbatim as HTTP 500 with `{"data":null,"message":"error with 'osd pool get': mon_cmd failed - unrecognized pool '<name>'\n"}` — a generic command failure, not a parsed field, but distinctively named ('unrecognized pool'), unlike ZfsPool's equivalent 'exit code 1' shape (deliberately left untyped — see zfs-pool-read-failure.test.ts: that message names no object kind at all, so typing it would risk folding an unrelated zpool-command failure into 'absent'). This shape states the honest status (404) while matching the wire's real one. Call site traced to source: `pve-manager` (git.proxmox.com/git/pve-manager.git, commit f6997e698c7933ea8e62319e2bf1bf7262daa56a, "bump version to 9.2.11" — the SDK's own pinned version, matching `pve-docs`'s own repoid for this snapshot) `PVE/API2/Ceph/Pool.pm` (~line 850), inside the `status` GET handler: `$rados->mon_command({ prefix => 'osd pool get', pool => "$pool", var => 'all' })`. `mon_cmd failed - unrecognized pool '<name>'` is Ceph's/librados's own wire text for a missing pool, not a PVE-authored string, so it was not independently re-derived from Perl source (there is none to read — it crosses into Ceph's own C++ `mon_command` implementation, out of scope for this pass). Measured: `taslabs-net/homeflare-kit`'s `packages/alchemy/src/proxmox/ceph-pool-write.test.ts:5-14`, live cluster TB4 `n2`, `GET /nodes/{node}/ceph/pool/{name}/status`, 2026-09-24, read-role, read-only probe. */
+export declare class CephPoolNotFound extends /*@__PURE__*/ CephPoolNotFound_base {
+}
 declare const ClusterNodeUnreachable_base: S.Class<ClusterNodeUnreachable, S.TaggedStruct<"ClusterNodeUnreachable", {
     readonly message: any;
 }>, import("effect/Cause").YieldableError> & (new (...args: any[]) => {
@@ -7022,7 +7042,7 @@ export declare const createNodeVzdump: API.OperationMethod<CreateNodeVzdumpReque
 export type CreateNodeWakeonlanError = ProxmoxOpError;
 /** Try to wake a node via 'wake on LAN' network packet. (root-privileged endpoint) */
 export declare const createNodeWakeonlan: API.OperationMethod<CreateNodeWakeonlanRequest, CreateNodeWakeonlanResponse, CreateNodeWakeonlanError, ProxmoxOpContext>;
-export type DeleteNodeCephFsError = ProxmoxOpError;
+export type DeleteNodeCephFsError = CephFsNotFound | ProxmoxOpError;
 /** Destroy a Ceph filesystem. Refuses if any PVE storage entry of type 'cephfs' still references the filesystem and is not disabled. Optionally also removes the storage entries and/or the underlying metadata and data pools. (root-privileged endpoint) */
 export declare const deleteNodeCephFs: API.OperationMethod<DeleteNodeCephFsRequest, DeleteNodeCephFsResponse, DeleteNodeCephFsError, ProxmoxOpContext>;
 export type DeleteNodeCephMdsError = ProxmoxOpError;
@@ -7163,7 +7183,7 @@ export declare const getNodeCephOsdMetadata: API.OperationMethod<GetNodeCephOsdM
 export type GetNodeCephPoolError = ProxmoxOpError;
 /** Pool index. */
 export declare const getNodeCephPool: API.OperationMethod<GetNodeCephPoolRequest, GetNodeCephPoolResponse, GetNodeCephPoolError, ProxmoxOpContext>;
-export type GetNodeCephPoolStatusError = ProxmoxOpError;
+export type GetNodeCephPoolStatusError = CephPoolNotFound | ProxmoxOpError;
 /** Show the current pool status. (root-privileged endpoint) */
 export declare const getNodeCephPoolStatus: API.OperationMethod<GetNodeCephPoolStatusRequest, GetNodeCephPoolStatusResponse, GetNodeCephPoolStatusError, ProxmoxOpContext>;
 export type GetNodeCephStatusError = ProxmoxOpError;