balena-cli 23.1.2 → 23.1.3

package/oclif.manifest.json

@@ -160,6 +160,56 @@
         "create.js"
       ]
     },
+    "block:create": {
+      "aliases": [],
+      "args": {
+        "name": {
+          "description": "block name",
+          "name": "name",
+          "required": true
+        }
+      },
+      "description": "Create an block.\n\nCreate a new balena block.\n\nYou can specify the organization the block should belong to using\nthe `--organization` option. The organization's handle, not its name,\nshould be provided. Organization handles can be listed with the\n`balena organization list` command.\n\nThe block's default device type is specified with the `--type` option.\nThe `balena device-type list` command can be used to list the available\ndevice types.\n\nInteractive dropdowns will be shown for selection if no device type or\norganization is specified and there are multiple options to choose from.\nIf there is a single option to choose from, it will be chosen automatically.\nThis interactive behavior can be disabled by explicitly specifying a device\ntype and organization.",
+      "examples": [
+        "$ balena block create MyBlock",
+        "$ balena block create MyBlock --organization mmyorg",
+        "$ balena block create MyBlock -o myorg --type raspberry-pi"
+      ],
+      "flags": {
+        "organization": {
+          "char": "o",
+          "description": "handle of the organization the block should belong to",
+          "name": "organization",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "type": {
+          "char": "t",
+          "description": "block device type (Check available types with `balena device-type list`)",
+          "name": "type",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "block:create",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "block",
+        "create.js"
+      ]
+    },
     "build": {
       "aliases": [],
       "args": {
@@ -362,56 +412,6 @@
         "index.js"
       ]
     },
-    "block:create": {
-      "aliases": [],
-      "args": {
-        "name": {
-          "description": "block name",
-          "name": "name",
-          "required": true
-        }
-      },
-      "description": "Create an block.\n\nCreate a new balena block.\n\nYou can specify the organization the block should belong to using\nthe `--organization` option. The organization's handle, not its name,\nshould be provided. Organization handles can be listed with the\n`balena organization list` command.\n\nThe block's default device type is specified with the `--type` option.\nThe `balena device-type list` command can be used to list the available\ndevice types.\n\nInteractive dropdowns will be shown for selection if no device type or\norganization is specified and there are multiple options to choose from.\nIf there is a single option to choose from, it will be chosen automatically.\nThis interactive behavior can be disabled by explicitly specifying a device\ntype and organization.",
-      "examples": [
-        "$ balena block create MyBlock",
-        "$ balena block create MyBlock --organization mmyorg",
-        "$ balena block create MyBlock -o myorg --type raspberry-pi"
-      ],
-      "flags": {
-        "organization": {
-          "char": "o",
-          "description": "handle of the organization the block should belong to",
-          "name": "organization",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "type": {
-          "char": "t",
-          "description": "block device type (Check available types with `balena device-type list`)",
-          "name": "type",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "block:create",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "block",
-        "create.js"
-      ]
-    },
     "config:generate": {
       "aliases": [],
       "args": {},
@@ -979,6 +979,45 @@
         "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": {
@@ -2199,45 +2238,6 @@
         "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": {},
@@ -2537,6 +2537,43 @@
         "set.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"
+      ]
+    },
     "fleet:create": {
       "aliases": [],
       "args": {
@@ -2879,43 +2916,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": {
@@ -3597,137 +3597,7 @@
         "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": {
+    "push": {
       "aliases": [],
       "args": {
         "fleetOrDevice": {
@@ -3892,6 +3762,136 @@
         "index.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"
+      ]
+    },
     "release:finalize": {
       "aliases": [],
       "args": {
@@ -4313,6 +4313,67 @@
         "index.js"
       ]
     },
+    "support": {
+      "aliases": [],
+      "args": {
+        "action": {
+          "description": "enable|disable support access",
+          "name": "action",
+          "options": [
+            "enable",
+            "disable"
+          ]
+        }
+      },
+      "description": "Grant or revoke support access for devices or fleets.\n\nGrant or revoke balena support agent access to devices or fleets\non balenaCloud. (This command does not apply to openBalena.)\nAccess will be automatically revoked once the specified duration has elapsed.\n\nDuration defaults to 24h, but can be specified using --duration flag in days\nor hours, e.g. '12h', '2d'.\n\nBoth --device and --fleet flags accept multiple values, specified as\na comma-separated list (with no spaces).\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 support enable --device ab346f,cd457a --duration 3d",
+        "balena support enable --fleet myFleet --duration 12h",
+        "balena support disable -f myorg/myfleet"
+      ],
+      "flags": {
+        "device": {
+          "char": "d",
+          "description": "comma-separated list (no spaces) of device UUIDs",
+          "name": "device",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "fleet": {
+          "char": "f",
+          "description": "comma-separated list (no spaces) of fleet names or slugs (preferred)",
+          "name": "fleet",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "duration": {
+          "char": "t",
+          "description": "length of time to enable support for, in (h)ours or (d)ays, e.g. 12h, 2d",
+          "name": "duration",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "support",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "support",
+        "index.js"
+      ]
+    },
     "ssh-key:add": {
       "aliases": [],
       "args": {
@@ -4448,67 +4509,6 @@
         "rm.js"
       ]
     },
-    "support": {
-      "aliases": [],
-      "args": {
-        "action": {
-          "description": "enable|disable support access",
-          "name": "action",
-          "options": [
-            "enable",
-            "disable"
-          ]
-        }
-      },
-      "description": "Grant or revoke support access for devices or fleets.\n\nGrant or revoke balena support agent access to devices or fleets\non balenaCloud. (This command does not apply to openBalena.)\nAccess will be automatically revoked once the specified duration has elapsed.\n\nDuration defaults to 24h, but can be specified using --duration flag in days\nor hours, e.g. '12h', '2d'.\n\nBoth --device and --fleet flags accept multiple values, specified as\na comma-separated list (with no spaces).\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 support enable --device ab346f,cd457a --duration 3d",
-        "balena support enable --fleet myFleet --duration 12h",
-        "balena support disable -f myorg/myfleet"
-      ],
-      "flags": {
-        "device": {
-          "char": "d",
-          "description": "comma-separated list (no spaces) of device UUIDs",
-          "name": "device",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "fleet": {
-          "char": "f",
-          "description": "comma-separated list (no spaces) of fleet names or slugs (preferred)",
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "duration": {
-          "char": "t",
-          "description": "length of time to enable support for, in (h)ours or (d)ays, e.g. 12h, 2d",
-          "name": "duration",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "support",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "support",
-        "index.js"
-      ]
-    },
     "tag:list": {
       "aliases": [],
       "args": {},
@@ -4729,53 +4729,53 @@
         "set.js"
       ]
     },
-    "util:available-drives": {
+    "whoami": {
       "aliases": [],
       "args": {},
-      "description": "List available drives.\n\nList available drives which are usable for writing an OS image to.\nDoes not list system drives.",
+      "description": "Display account information for current user.\n\nGet the username and email address of the currently logged in user.",
+      "examples": [
+        "$ balena whoami"
+      ],
       "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "util:available-drives",
+      "id": "whoami",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "offlineCompatible": true,
+      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "util",
-        "available-drives.js"
+        "whoami",
+        "index.js"
       ]
     },
-    "whoami": {
+    "util:available-drives": {
       "aliases": [],
       "args": {},
-      "description": "Display account information for current user.\n\nGet the username and email address of the currently logged in user.",
-      "examples": [
-        "$ balena whoami"
-      ],
+      "description": "List available drives.\n\nList available drives which are usable for writing an OS image to.\nDoes not list system drives.",
       "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "whoami",
+      "id": "util:available-drives",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "authenticated": true,
+      "offlineCompatible": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "whoami",
-        "index.js"
+        "util",
+        "available-drives.js"
       ]
     }
   },
-  "version": "23.1.2"
+  "version": "23.1.3"
 }