@truenas/api-client 2.0.1 → 3.0.0

package/dist/index.js

@@ -2519,7 +2519,6 @@ __export(v26_0_0_exports, {
   Aclmode: () => Aclmode,
   Acltype: () => Acltype,
   Advpowermgmt: () => Advpowermgmt,
-  Algorithm: () => Algorithm,
   AppContainerDetailsState: () => AppContainerDetailsState,
   AppContainerDetailsStateInput: () => AppContainerDetailsStateInput,
   Atime: () => Atime,
@@ -2657,11 +2656,13 @@ var ContainerNICDeviceTypeInput = {
 };
 var ContainerStatusState = {
   Running: "RUNNING",
-  Stopped: "STOPPED"
+  Stopped: "STOPPED",
+  Suspended: "SUSPENDED"
 };
 var ContainerStatusStateInput = {
   Running: "RUNNING",
-  Stopped: "STOPPED"
+  Stopped: "STOPPED",
+  Suspended: "SUSPENDED"
 };
 var Feature2 = {
   Apps: "APPS",
@@ -2741,7 +2742,6 @@ __export(v27_0_0_exports, {
   Aclmode: () => Aclmode,
   Acltype: () => Acltype,
   Advpowermgmt: () => Advpowermgmt,
-  Algorithm: () => Algorithm,
   AppContainerDetailsState: () => AppContainerDetailsState,
   AppContainerDetailsStateInput: () => AppContainerDetailsStateInput,
   Atime: () => Atime,
@@ -3064,6 +3064,10 @@ var AppState = /* @__PURE__ */ ((AppState2) => {
   AppState2["Stopped"] = "STOPPED";
   AppState2["Stopping"] = "STOPPING";
   AppState2["Deploying"] = "DEPLOYING";
+  AppState2["Suspended"] = "SUSPENDED";
+  AppState2["Suspending"] = "SUSPENDING";
+  AppState2["Error"] = "ERROR";
+  AppState2["Unknown"] = "UNKNOWN";
   return AppState2;
 })(AppState || {});
 
@@ -3074,7 +3078,10 @@ function toAppState(state) {
       return "RUNNING" /* Running */;
     case "STOPPED":
       return "STOPPED" /* Stopped */;
+    // `ABORTING` is v25.10 only: the instance is being forced down, which ends
+    // at `STOPPED` and is what `Stopping` already means.
     case "STOPPING":
+    case "ABORTING":
       return "STOPPING" /* Stopping */;
     // `STARTING` is v25.10 `virt.instance` only, and folding it into `Stopped`
     // told callers a container that is coming up is at rest — enough for a UI
@@ -3083,8 +3090,35 @@ function toAppState(state) {
     case "STARTING":
     case "DEPLOYING":
       return "DEPLOYING" /* Deploying */;
+    // v25.10's freezer states are the same idea as v26's `SUSPENDED`: the
+    // processes are paused, not exited. `FROZEN` is that pause completed, so it
+    // and `SUSPENDED` are the same answer.
+    case "SUSPENDED":
+    case "FROZEN":
+      return "SUSPENDED" /* Suspended */;
+    // `FREEZING` is on the way there and not there yet. It used to answer
+    // `Suspended`, defended by analogy with `STARTING` — but `STARTING` maps to
+    // `Deploying`, which is itself an in-progress word, so the analogy ran the
+    // wrong way. Answering `Suspended` tells a caller polling for "the memory
+    // is quiesced" that it is, one poll before it is true: the same false
+    // claim this mapping was rewritten to stop making, one state along.
+    // `ABORTING` had `Stopping` to land on; the freeze path needed its own.
+    case "FREEZING":
+      return "SUSPENDING" /* Suspending */;
+    // `THAWED` is the freezer lifted: the processes are scheduled again, so
+    // this is `RUNNING` reported through the transition rather than a state a
+    // caller should act on differently.
+    case "THAWED":
+      return "RUNNING" /* Running */;
+    case "ERROR":
+      return "ERROR" /* Error */;
+    // `UNKNOWN` is middleware's own word for it, and anything unrecognised is
+    // the same situation: a state this mapping has no word for. Neither is
+    // evidence the container is stopped.
+    case "UNKNOWN":
+      return "UNKNOWN" /* Unknown */;
     default:
-      return "STOPPED" /* Stopped */;
+      return "UNKNOWN" /* Unknown */;
   }
 }