balena-cli 23.2.21 → 23.2.22

package/oclif.manifest.json

@@ -979,45 +979,6 @@
         "index.js"
       ]
     },
-    "device-type:list": {
-      "aliases": [],
-      "args": {},
-      "description": "List the device types supported by balena (like 'raspberrypi3' or 'intel-nuc').\n\nList the device types supported by balena (like 'raspberrypi3' or 'intel-nuc').\n\nBy default, only actively supported device types are listed.\nThe --all option can be used to list all device types, including those that are\nno longer supported by balena.",
-      "examples": [
-        "$ balena device-type list",
-        "$ balena device-type list --all"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "all": {
-          "description": "include device types no longer supported by balena",
-          "name": "all",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "device-type:list",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "device-type",
-        "list.js"
-      ]
-    },
     "device:deactivate": {
       "aliases": [],
       "args": {
@@ -2238,6 +2199,45 @@
         "tunnel.js"
       ]
     },
+    "device-type:list": {
+      "aliases": [],
+      "args": {},
+      "description": "List the device types supported by balena (like 'raspberrypi3' or 'intel-nuc').\n\nList the device types supported by balena (like 'raspberrypi3' or 'intel-nuc').\n\nBy default, only actively supported device types are listed.\nThe --all option can be used to list all device types, including those that are\nno longer supported by balena.",
+      "examples": [
+        "$ balena device-type list",
+        "$ balena device-type list --all"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "all": {
+          "description": "include device types no longer supported by balena",
+          "name": "all",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "device-type:list",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "device-type",
+        "list.js"
+      ]
+    },
     "env:list": {
       "aliases": [],
       "args": {},
@@ -2879,43 +2879,6 @@
         "track-latest.js"
       ]
     },
-    "internal:osinit": {
-      "aliases": [],
-      "args": {
-        "image": {
-          "name": "image",
-          "required": true
-        },
-        "type": {
-          "name": "type",
-          "required": true
-        },
-        "config": {
-          "name": "config",
-          "required": true
-        }
-      },
-      "description": "Do actual init of the device with the preconfigured os image.\n\nDon't use this command directly!\nUse `balena os initialize <image>` instead.",
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hidden": true,
-      "hiddenAliases": [],
-      "id": "internal:osinit",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "root": true,
-      "offlineCompatible": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "internal",
-        "osinit.js"
-      ]
-    },
     "join": {
       "aliases": [],
       "args": {
@@ -2969,6 +2932,43 @@
         "index.js"
       ]
     },
+    "internal:osinit": {
+      "aliases": [],
+      "args": {
+        "image": {
+          "name": "image",
+          "required": true
+        },
+        "type": {
+          "name": "type",
+          "required": true
+        },
+        "config": {
+          "name": "config",
+          "required": true
+        }
+      },
+      "description": "Do actual init of the device with the preconfigured os image.\n\nDon't use this command directly!\nUse `balena os initialize <image>` instead.",
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hidden": true,
+      "hiddenAliases": [],
+      "id": "internal:osinit",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "root": true,
+      "offlineCompatible": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "internal",
+        "osinit.js"
+      ]
+    },
     "leave": {
       "aliases": [],
       "args": {
@@ -3258,115 +3258,245 @@
         "list.js"
       ]
     },
-    "os:configure": {
+    "preload": {
       "aliases": [],
       "args": {
         "image": {
-          "description": "path to a balenaOS image file, e.g. \"rpi3.img\"",
+          "description": "the image file path",
           "name": "image",
           "required": true
         }
       },
-      "description": "Configure a previously downloaded balenaOS image.\n\nConfigure a previously downloaded balenaOS image for a specific device type\nor fleet.\n\nConfiguration settings such as WiFi authentication will be taken from the\nfollowing sources, in precedence order:\n1. Command-line options like `--config-wifi-ssid`\n2. A given `config.json` file specified with the `--config` option.\n3. User input through interactive prompts (text menus).\n\nThe --device-type option is used to override the fleet's default device type,\nin case of a fleet with mixed device types.\n\nThe '--dev' option is used to configure balenaOS to operate in development mode,\nallowing unauthenticated root ssh access and exposing network ports such as\nbalenaEngine's 2375 (unencrypted). This option causes `\"developmentMode\": true`\nto be inserted in the 'config.json' file in the image's boot partition. Development\nmode (as a configurable option) is applicable to balenaOS releases from early\n2022. Older releases have separate development and production balenaOS images\nthat cannot be reconfigured through 'config.json' or the '--dev' option. Do not\nconfuse the balenaOS \"development mode\" with a device's \"local mode\", the latter\nbeing a supervisor feature that allows the \"balena push\" command to push a user's\napplication directly to a device in the local network.\n\nThe '--secureBoot' option is used to configure a balenaOS installer image to opt-in\nsecure boot and disk encryption.\n\nThe --system-connection (-c) option is used to inject NetworkManager connection\nprofiles for additional network interfaces, such as cellular/GSM or additional\nWiFi or ethernet connections. This option may be passed multiple times in case there\nare multiple files to inject. See connection profile examples and reference at:\nhttps://www.balena.io/docs/reference/OS/network/2.x/\nhttps://developer.gnome.org/NetworkManager/stable/ref-settings.html\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).",
+      "description": "Preload a release on a disk image (or Edison zip archive).\n\nPreload a release (service images/containers) from a balena fleet, and optionally\na balenaOS splash screen, in a previously downloaded '.img' balenaOS image file\nin the local disk (a zip file is only accepted for the Intel Edison device type).\nAfter preloading, the balenaOS image file can be flashed to a device's SD card.\nWhen the device boots, it will not need to download the release, as it was\npreloaded. This is usually combined with release pinning\n(https://www.balena.io/docs/learn/deploy/release-strategy/release-policy/)\nto avoid the device downloading a newer release straight away, if available.\nCheck also the Preloading and Preregistering section of the balena CLI's advanced\nmasterclass document:\nhttps://www.balena.io/docs/learn/more/masterclasses/advanced-cli/#5-preloading-and-preregistering\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).\n\nNote that the this command requires Docker to be installed, as further detailed\nin the balena CLI's installation instructions:\nhttps://github.com/balena-io/balena-cli/blob/master/INSTALL.md\nThe `--dockerHost` and `--dockerPort` flags allow a remote Docker engine to\nbe used, however the image file must be accessible to the remote Docker engine\non the same path given on the command line. This is because Docker's bind mount\nfeature is used to \"share\" the image with a container that performs the preload.",
       "examples": [
-        "$ balena os configure ../path/rpi3.img --device 7cf02a6",
-        "$ balena os configure ../path/rpi3.img --fleet myorg/myfleet",
-        "$ balena os configure ../path/rpi3.img -f myorg/myfleet --device-type raspberrypi3",
-        "$ balena os configure ../path/rpi3.img --config myWifiConfig.json"
+        "$ balena preload balena.img --fleet MyFleet --commit e1f2592fc6ee949e68756d4f4a48e49bff8d72a0",
+        "$ balena preload balena.img --fleet myorg/myfleet --splash-image image.png",
+        "$ balena preload balena.img"
       ],
       "flags": {
         "fleet": {
           "char": "f",
           "description": "fleet name or slug (preferred)",
-          "exclusive": [
-            "device",
-            "config"
-          ],
           "name": "fleet",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "device": {
-          "char": "d",
-          "description": "device UUID",
-          "exclusive": [
-            "fleet",
-            "device-type",
-            "config",
-            "provisioning-key-name",
-            "provisioning-key-expiry-date"
-          ],
-          "name": "device",
+        "commit": {
+          "char": "c",
+          "description": "The commit hash of the release to preload. Use \"current\" to specify the current\nrelease (ignored if no appId is given). The current release is usually also the\nlatest, but can be pinned to a specific release. See:\nhttps://www.balena.io/docs/learn/deploy/release-strategy/release-policy/\nhttps://www.balena.io/docs/learn/more/masterclasses/fleet-management/#63-pin-using-the-api\nhttps://github.com/balena-io-examples/staged-releases",
+          "name": "commit",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "config": {
-          "description": "path to a pre-generated config.json file to be injected in the OS image",
-          "exclusive": [
-            "fleet",
-            "device",
-            "advanced",
-            "config-app-update-poll-interval",
-            "config-network",
-            "config-wifi-key",
-            "config-wifi-ssid",
-            "dev",
-            "secureBoot",
-            "device-type",
-            "initial-device-name",
-            "provisioning-key-name",
-            "provisioning-key-expiry-date"
-          ],
-          "name": "config",
+        "splash-image": {
+          "char": "s",
+          "description": "path to a png image to replace the splash screen",
+          "name": "splash-image",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "advanced": {
-          "char": "v",
-          "description": "ask advanced configuration questions (when in interactive mode)",
-          "name": "advanced",
+        "dont-check-arch": {
+          "description": "disable architecture compatibility check between image and fleet",
+          "name": "dont-check-arch",
           "allowNo": false,
           "type": "boolean"
         },
-        "config-app-update-poll-interval": {
-          "description": "supervisor cloud polling interval in minutes (e.g. for variable updates)",
-          "name": "config-app-update-poll-interval",
+        "pin-device-to-release": {
+          "char": "p",
+          "description": "pin the preloaded device to the preloaded release on provision",
+          "name": "pin-device-to-release",
+          "allowNo": true,
+          "type": "boolean"
+        },
+        "additional-space": {
+          "description": "expand the image by this amount of bytes instead of automatically estimating the required amount",
+          "name": "additional-space",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "config-network": {
-          "description": "device network type (non-interactive configuration)",
-          "name": "config-network",
+        "add-certificate": {
+          "description": "Add the given certificate (in PEM format) to /etc/ssl/certs in the preloading container.\nThe file name must end with '.crt' and must not be already contained in the preloader's\n/etc/ssl/certs folder.\nCan be repeated to add multiple certificates.",
+          "name": "add-certificate",
           "hasDynamicHelp": false,
-          "multiple": false,
-          "options": [
-            "ethernet",
-            "wifi"
-          ],
+          "multiple": true,
           "type": "option"
         },
-        "config-wifi-key": {
-          "description": "WiFi key (password) (non-interactive configuration)",
-          "name": "config-wifi-key",
+        "docker": {
+          "char": "P",
+          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
+          "name": "docker",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "config-wifi-ssid": {
-          "description": "WiFi SSID (network name) (non-interactive configuration)",
-          "name": "config-wifi-ssid",
+        "dockerHost": {
+          "char": "h",
+          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
+          "name": "dockerHost",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "dev": {
-          "description": "Configure balenaOS to operate in development mode",
-          "name": "dev",
-          "allowNo": false,
+        "dockerPort": {
+          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
+          "name": "dockerPort",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "ca": {
+          "description": "Docker host TLS certificate authority file",
+          "name": "ca",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "cert": {
+          "description": "Docker host TLS certificate file",
+          "name": "cert",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "key": {
+          "description": "Docker host TLS key file",
+          "name": "key",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "preload",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "primary": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "preload",
+        "index.js"
+      ]
+    },
+    "os:configure": {
+      "aliases": [],
+      "args": {
+        "image": {
+          "description": "path to a balenaOS image file, e.g. \"rpi3.img\"",
+          "name": "image",
+          "required": true
+        }
+      },
+      "description": "Configure a previously downloaded balenaOS image.\n\nConfigure a previously downloaded balenaOS image for a specific device type\nor fleet.\n\nConfiguration settings such as WiFi authentication will be taken from the\nfollowing sources, in precedence order:\n1. Command-line options like `--config-wifi-ssid`\n2. A given `config.json` file specified with the `--config` option.\n3. User input through interactive prompts (text menus).\n\nThe --device-type option is used to override the fleet's default device type,\nin case of a fleet with mixed device types.\n\nThe '--dev' option is used to configure balenaOS to operate in development mode,\nallowing unauthenticated root ssh access and exposing network ports such as\nbalenaEngine's 2375 (unencrypted). This option causes `\"developmentMode\": true`\nto be inserted in the 'config.json' file in the image's boot partition. Development\nmode (as a configurable option) is applicable to balenaOS releases from early\n2022. Older releases have separate development and production balenaOS images\nthat cannot be reconfigured through 'config.json' or the '--dev' option. Do not\nconfuse the balenaOS \"development mode\" with a device's \"local mode\", the latter\nbeing a supervisor feature that allows the \"balena push\" command to push a user's\napplication directly to a device in the local network.\n\nThe '--secureBoot' option is used to configure a balenaOS installer image to opt-in\nsecure boot and disk encryption.\n\nThe --system-connection (-c) option is used to inject NetworkManager connection\nprofiles for additional network interfaces, such as cellular/GSM or additional\nWiFi or ethernet connections. This option may be passed multiple times in case there\nare multiple files to inject. See connection profile examples and reference at:\nhttps://www.balena.io/docs/reference/OS/network/2.x/\nhttps://developer.gnome.org/NetworkManager/stable/ref-settings.html\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).",
+      "examples": [
+        "$ balena os configure ../path/rpi3.img --device 7cf02a6",
+        "$ balena os configure ../path/rpi3.img --fleet myorg/myfleet",
+        "$ balena os configure ../path/rpi3.img -f myorg/myfleet --device-type raspberrypi3",
+        "$ balena os configure ../path/rpi3.img --config myWifiConfig.json"
+      ],
+      "flags": {
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "exclusive": [
+            "device",
+            "config"
+          ],
+          "name": "fleet",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "device": {
+          "char": "d",
+          "description": "device UUID",
+          "exclusive": [
+            "fleet",
+            "device-type",
+            "config",
+            "provisioning-key-name",
+            "provisioning-key-expiry-date"
+          ],
+          "name": "device",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "config": {
+          "description": "path to a pre-generated config.json file to be injected in the OS image",
+          "exclusive": [
+            "fleet",
+            "device",
+            "advanced",
+            "config-app-update-poll-interval",
+            "config-network",
+            "config-wifi-key",
+            "config-wifi-ssid",
+            "dev",
+            "secureBoot",
+            "device-type",
+            "initial-device-name",
+            "provisioning-key-name",
+            "provisioning-key-expiry-date"
+          ],
+          "name": "config",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "advanced": {
+          "char": "v",
+          "description": "ask advanced configuration questions (when in interactive mode)",
+          "name": "advanced",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "config-app-update-poll-interval": {
+          "description": "supervisor cloud polling interval in minutes (e.g. for variable updates)",
+          "name": "config-app-update-poll-interval",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "config-network": {
+          "description": "device network type (non-interactive configuration)",
+          "name": "config-network",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "ethernet",
+            "wifi"
+          ],
+          "type": "option"
+        },
+        "config-wifi-key": {
+          "description": "WiFi key (password) (non-interactive configuration)",
+          "name": "config-wifi-key",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "config-wifi-ssid": {
+          "description": "WiFi SSID (network name) (non-interactive configuration)",
+          "name": "config-wifi-ssid",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "dev": {
+          "description": "Configure balenaOS to operate in development mode",
+          "name": "dev",
+          "allowNo": false,
           "type": "boolean"
         },
         "secureBoot": {
@@ -3597,136 +3727,6 @@
         "versions.js"
       ]
     },
-    "preload": {
-      "aliases": [],
-      "args": {
-        "image": {
-          "description": "the image file path",
-          "name": "image",
-          "required": true
-        }
-      },
-      "description": "Preload a release on a disk image (or Edison zip archive).\n\nPreload a release (service images/containers) from a balena fleet, and optionally\na balenaOS splash screen, in a previously downloaded '.img' balenaOS image file\nin the local disk (a zip file is only accepted for the Intel Edison device type).\nAfter preloading, the balenaOS image file can be flashed to a device's SD card.\nWhen the device boots, it will not need to download the release, as it was\npreloaded. This is usually combined with release pinning\n(https://www.balena.io/docs/learn/deploy/release-strategy/release-policy/)\nto avoid the device downloading a newer release straight away, if available.\nCheck also the Preloading and Preregistering section of the balena CLI's advanced\nmasterclass document:\nhttps://www.balena.io/docs/learn/more/masterclasses/advanced-cli/#5-preloading-and-preregistering\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).\n\nNote that the this command requires Docker to be installed, as further detailed\nin the balena CLI's installation instructions:\nhttps://github.com/balena-io/balena-cli/blob/master/INSTALL.md\nThe `--dockerHost` and `--dockerPort` flags allow a remote Docker engine to\nbe used, however the image file must be accessible to the remote Docker engine\non the same path given on the command line. This is because Docker's bind mount\nfeature is used to \"share\" the image with a container that performs the preload.",
-      "examples": [
-        "$ balena preload balena.img --fleet MyFleet --commit e1f2592fc6ee949e68756d4f4a48e49bff8d72a0",
-        "$ balena preload balena.img --fleet myorg/myfleet --splash-image image.png",
-        "$ balena preload balena.img"
-      ],
-      "flags": {
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "commit": {
-          "char": "c",
-          "description": "The commit hash of the release to preload. Use \"current\" to specify the current\nrelease (ignored if no appId is given). The current release is usually also the\nlatest, but can be pinned to a specific release. See:\nhttps://www.balena.io/docs/learn/deploy/release-strategy/release-policy/\nhttps://www.balena.io/docs/learn/more/masterclasses/fleet-management/#63-pin-using-the-api\nhttps://github.com/balena-io-examples/staged-releases",
-          "name": "commit",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "splash-image": {
-          "char": "s",
-          "description": "path to a png image to replace the splash screen",
-          "name": "splash-image",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dont-check-arch": {
-          "description": "disable architecture compatibility check between image and fleet",
-          "name": "dont-check-arch",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "pin-device-to-release": {
-          "char": "p",
-          "description": "pin the preloaded device to the preloaded release on provision",
-          "name": "pin-device-to-release",
-          "allowNo": true,
-          "type": "boolean"
-        },
-        "additional-space": {
-          "description": "expand the image by this amount of bytes instead of automatically estimating the required amount",
-          "name": "additional-space",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "add-certificate": {
-          "description": "Add the given certificate (in PEM format) to /etc/ssl/certs in the preloading container.\nThe file name must end with '.crt' and must not be already contained in the preloader's\n/etc/ssl/certs folder.\nCan be repeated to add multiple certificates.",
-          "name": "add-certificate",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "docker": {
-          "char": "P",
-          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
-          "name": "docker",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dockerHost": {
-          "char": "h",
-          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
-          "name": "dockerHost",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dockerPort": {
-          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
-          "name": "dockerPort",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "ca": {
-          "description": "Docker host TLS certificate authority file",
-          "name": "ca",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "cert": {
-          "description": "Docker host TLS certificate file",
-          "name": "cert",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "key": {
-          "description": "Docker host TLS key file",
-          "name": "key",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "preload",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "primary": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "preload",
-        "index.js"
-      ]
-    },
     "push": {
       "aliases": [],
       "args": {
@@ -3866,54 +3866,212 @@
           "name": "draft",
           "allowNo": false,
           "type": "boolean"
-        },
-        "note": {
-          "description": "The notes for this release",
-          "name": "note",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
+        },
+        "note": {
+          "description": "The notes for this release",
+          "name": "note",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "push",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "primary": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "push",
+        "index.js"
+      ]
+    },
+    "release:finalize": {
+      "aliases": [],
+      "args": {
+        "commitOrId": {
+          "description": "the commit or ID of the release to finalize",
+          "name": "commitOrId",
+          "required": true
+        }
+      },
+      "description": "Finalize a release.\n\nFinalize a release. Releases can be \"draft\" or \"final\", and this command\nchanges a draft release into a final release. Draft releases can be created\nwith the `--draft` option of the `balena build` or `balena deploy`\ncommands.\n\nDraft releases are not automatically deployed to devices tracking the latest\nrelease. For a draft release to be deployed to a device, the device should be\nexplicity pinned to that release. Conversely, final releases may trigger immediate\ndeployment to unpinned devices (subject to a device's  polling period) and, for\nthis reason, final releases cannot be changed back to draft status.",
+      "examples": [
+        "$ balena release finalize a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release finalize 1234567"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "release:finalize",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "release",
+        "finalize.js"
+      ]
+    },
+    "release": {
+      "aliases": [],
+      "args": {
+        "commitOrId": {
+          "description": "the commit or ID of the release to get information",
+          "name": "commitOrId",
+          "required": true
+        }
+      },
+      "description": "Get info for a release.",
+      "examples": [
+        "$ balena release a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release 1234567"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "composition": {
+          "char": "c",
+          "description": "Return the release composition",
+          "name": "composition",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "release",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": true,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "release",
+        "index.js"
+      ]
+    },
+    "release:invalidate": {
+      "aliases": [],
+      "args": {
+        "commitOrId": {
+          "description": "the commit or ID of the release to invalidate",
+          "name": "commitOrId",
+          "required": true
+        }
+      },
+      "description": "Invalidate a release.\n\nInvalidate a release.\n\nInvalid releases are not automatically deployed to devices tracking the latest\nrelease. For an invalid release to be deployed to a device, the device should be\nexplicity pinned to that release.",
+      "examples": [
+        "$ balena release invalidate a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release invalidate 1234567"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "release:invalidate",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "release",
+        "invalidate.js"
+      ]
+    },
+    "release:list": {
+      "aliases": [],
+      "args": {
+        "fleet": {
+          "description": "fleet name or slug (preferred)",
+          "name": "fleet",
+          "required": true
+        }
+      },
+      "description": "List all releases of a fleet.\n\nList all releases of the given fleet.\n\nFleets may be specified by fleet name or slug. Slugs are recommended because\nthey are unique and unambiguous. Slugs can be listed with the `balena fleet list`\ncommand. Note that slugs may change if the fleet is renamed. Fleet names are\nnot unique and may result in \"Fleet is ambiguous\" errors at any time (even if\n\"it used to work in the past\"), for example if the name clashes with a newly\ncreated public/open fleet, or with fleets from other balena accounts that you\nmay be invited to join under any role.  For this reason, fleet names are\nespecially discouraged in scripts (e.g. CI environments).",
+      "examples": [
+        "$ balena release list myorg/myfleet"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "push",
+      "id": "release:list",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
-      "enableJsonFlag": false,
-      "primary": true,
+      "enableJsonFlag": true,
+      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "push",
-        "index.js"
+        "release",
+        "list.js"
       ]
     },
-    "settings": {
+    "release:validate": {
       "aliases": [],
-      "args": {},
-      "description": "Print current settings.\n\nUse this command to display the current balena CLI settings.",
+      "args": {
+        "commitOrId": {
+          "description": "the commit or ID of the release to validate",
+          "name": "commitOrId",
+          "required": true
+        }
+      },
+      "description": "Validate a release.\n\nValidate a release.\n\nValid releases are automatically deployed to devices tracking the latest\nrelease if they are finalized.",
       "examples": [
-        "$ balena settings"
+        "$ balena release validate a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release validate 1234567"
       ],
       "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "settings",
+      "id": "release:validate",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
+      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "settings",
-        "index.js"
+        "release",
+        "validate.js"
       ]
     },
     "release-asset:delete": {
@@ -4131,188 +4289,30 @@
         "upload.js"
       ]
     },
-    "release:finalize": {
+    "settings": {
       "aliases": [],
-      "args": {
-        "commitOrId": {
-          "description": "the commit or ID of the release to finalize",
-          "name": "commitOrId",
-          "required": true
-        }
-      },
-      "description": "Finalize a release.\n\nFinalize a release. Releases can be \"draft\" or \"final\", and this command\nchanges a draft release into a final release. Draft releases can be created\nwith the `--draft` option of the `balena build` or `balena deploy`\ncommands.\n\nDraft releases are not automatically deployed to devices tracking the latest\nrelease. For a draft release to be deployed to a device, the device should be\nexplicity pinned to that release. Conversely, final releases may trigger immediate\ndeployment to unpinned devices (subject to a device's  polling period) and, for\nthis reason, final releases cannot be changed back to draft status.",
+      "args": {},
+      "description": "Print current settings.\n\nUse this command to display the current balena CLI settings.",
       "examples": [
-        "$ balena release finalize a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release finalize 1234567"
+        "$ balena settings"
       ],
       "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release:finalize",
+      "id": "settings",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "release",
-        "finalize.js"
-      ]
-    },
-    "release": {
-      "aliases": [],
-      "args": {
-        "commitOrId": {
-          "description": "the commit or ID of the release to get information",
-          "name": "commitOrId",
-          "required": true
-        }
-      },
-      "description": "Get info for a release.",
-      "examples": [
-        "$ balena release a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release 1234567"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "composition": {
-          "char": "c",
-          "description": "Return the release composition",
-          "name": "composition",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "release",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": true,
-      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "release",
+        "settings",
         "index.js"
       ]
     },
-    "release:invalidate": {
-      "aliases": [],
-      "args": {
-        "commitOrId": {
-          "description": "the commit or ID of the release to invalidate",
-          "name": "commitOrId",
-          "required": true
-        }
-      },
-      "description": "Invalidate a release.\n\nInvalidate a release.\n\nInvalid releases are not automatically deployed to devices tracking the latest\nrelease. For an invalid release to be deployed to a device, the device should be\nexplicity pinned to that release.",
-      "examples": [
-        "$ balena release invalidate a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release invalidate 1234567"
-      ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "release:invalidate",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "release",
-        "invalidate.js"
-      ]
-    },
-    "release:list": {
-      "aliases": [],
-      "args": {
-        "fleet": {
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
-          "required": true
-        }
-      },
-      "description": "List all releases of a fleet.\n\nList all releases of the given fleet.\n\nFleets may be specified by fleet name or slug. Slugs are recommended because\nthey are unique and unambiguous. Slugs can be listed with the `balena fleet list`\ncommand. Note that slugs may change if the fleet is renamed. Fleet names are\nnot unique and may result in \"Fleet is ambiguous\" errors at any time (even if\n\"it used to work in the past\"), for example if the name clashes with a newly\ncreated public/open fleet, or with fleets from other balena accounts that you\nmay be invited to join under any role.  For this reason, fleet names are\nespecially discouraged in scripts (e.g. CI environments).",
-      "examples": [
-        "$ balena release list myorg/myfleet"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "release:list",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": true,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "release",
-        "list.js"
-      ]
-    },
-    "release:validate": {
-      "aliases": [],
-      "args": {
-        "commitOrId": {
-          "description": "the commit or ID of the release to validate",
-          "name": "commitOrId",
-          "required": true
-        }
-      },
-      "description": "Validate a release.\n\nValidate a release.\n\nValid releases are automatically deployed to devices tracking the latest\nrelease if they are finalized.",
-      "examples": [
-        "$ balena release validate a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release validate 1234567"
-      ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "release:validate",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "release",
-        "validate.js"
-      ]
-    },
     "support": {
       "aliases": [],
       "args": {
@@ -4777,5 +4777,5 @@
       ]
     }
   },
-  "version": "23.2.21"
+  "version": "23.2.22"
 }