balena-cli 23.2.14 → 23.2.15-build-update-compose-7-3-0-97bf26975807627a264274621ffcf8380aea838e-1

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": {},
@@ -1018,54 +1018,16 @@
         "list.js"
       ]
     },
-    "device:deactivate": {
-      "aliases": [],
-      "args": {
-        "uuid": {
-          "description": "the UUID of the device to be deactivated",
-          "name": "uuid",
-          "required": true
-        }
-      },
-      "description": "Deactivate a device.\n\nDeactivate a device.\n\nNote this command asks for confirmation interactively.\nYou can avoid this by passing the `--yes` option.",
-      "examples": [
-        "$ balena device deactivate 7cf02a6",
-        "$ balena device deactivate 7cf02a6 --yes"
-      ],
-      "flags": {
-        "yes": {
-          "char": "y",
-          "description": "answer \"yes\" to all questions (non interactive use)",
-          "name": "yes",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "device:deactivate",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "device",
-        "deactivate.js"
-      ]
-    },
-    "device:detect": {
+    "env:list": {
       "aliases": [],
       "args": {},
-      "description": "Scan for balenaOS devices on your local network.\n\nScan for balenaOS devices on your local network.\n\nThe output includes device information collected through balenaEngine for\ndevices running a development image of balenaOS. Devices running a production\nimage do not expose balenaEngine (on TCP port 2375), which is why less\ninformation is printed about them.",
+      "description": "List the environment or config variables of a fleet, device or service.\n\nList the environment or configuration variables of a fleet, device or\nservice, as selected by the respective command-line options. (A service\ncorresponds to a Docker image/container in a microservices fleet.)\n\nThe results include fleet-wide (multiple devices), device-specific (multiple\nservices on a specific device) and service-specific variables that apply to the\nselected fleet, device or service. It can be thought of as including inherited\nvariables; for example, a service inherits device-wide variables, and a device\ninherits fleet-wide variables.\n\nThe printed output may include DEVICE and/or SERVICE columns to distinguish\nbetween fleet-wide, device-specific and service-specific variables.\nAn asterisk in these columns indicates that the variable applies to\n\"all devices\" or \"all services\".\n\nThe --config option is used to list \"configuration variables\" that control\nbalena platform features, as opposed to custom environment variables defined\nby the user. The --config and the --service options are mutually exclusive\nbecause configuration variables cannot be set for specific services.\n\nWhen --json is used, an empty JSON array ([]) is printed instead of an error \nmessage when no variables exist for the given query. When querying variables \nfor a device, note that the fleet name may be null in JSON output \n(or 'N/A' in tabular output) if the fleet that the device belonged to is no \nlonger accessible by the current user (for example, in case the current user \nwas removed from the fleet by the fleet's owner).\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 device detect",
-        "$ balena device detect --timeout 120",
-        "$ balena device detect --verbose"
+        "$ balena env list --fleet myorg/myfleet",
+        "$ balena env list --fleet MyFleet --service MyService",
+        "$ balena env list --fleet MyFleet --config",
+        "$ balena env list --device 7cf02a6",
+        "$ balena env list --device 7cf02a6 --service MyService"
       ],
       "flags": {
         "json": {
@@ -1075,17 +1037,45 @@
           "allowNo": false,
           "type": "boolean"
         },
-        "verbose": {
-          "char": "v",
-          "description": "display full info",
-          "name": "verbose",
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "exclusive": [
+            "device"
+          ],
+          "name": "fleet",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "config": {
+          "char": "c",
+          "description": "show configuration variables only",
+          "exclusive": [
+            "service"
+          ],
+          "name": "config",
           "allowNo": false,
           "type": "boolean"
         },
-        "timeout": {
-          "char": "t",
-          "description": "scan timeout in seconds",
-          "name": "timeout",
+        "device": {
+          "char": "d",
+          "description": "device UUID",
+          "exclusive": [
+            "fleet"
+          ],
+          "name": "device",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "service": {
+          "char": "s",
+          "description": "service name",
+          "exclusive": [
+            "config"
+          ],
+          "name": "service",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -1093,191 +1083,255 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "device:detect",
+      "id": "env:list",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": true,
-      "primary": true,
-      "root": true,
-      "offlineCompatible": true,
-      "dockerInfoProperties": [
-        "Containers",
-        "ContainersRunning",
-        "ContainersPaused",
-        "ContainersStopped",
-        "Images",
-        "Driver",
-        "SystemTime",
-        "KernelVersion",
-        "OperatingSystem",
-        "Architecture"
-      ],
-      "dockerVersionProperties": [
-        "Version",
-        "ApiVersion"
-      ],
-      "noDevicesFoundMessage": "Could not find any balenaOS devices on the local network.",
-      "windowsTipMessage": "\n\nNote for Windows users:\n  The 'device detect' command relies on the Bonjour service. Check whether Bonjour is\n  installed (Control Panel > Programs and Features). If not, you can download\n  Bonjour for Windows (included with Bonjour Print Services) from here:\n  https://support.apple.com/kb/DL999\n\n  After installing Bonjour, restart your PC and run the 'balena device detect' command\n  again.",
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "device",
-        "detect.js"
+        "env",
+        "list.js"
       ]
     },
-    "device:identify": {
+    "env:rename": {
       "aliases": [],
       "args": {
-        "uuid": {
-          "description": "the uuid of the device to identify",
-          "name": "uuid",
+        "id": {
+          "description": "variable's numeric database ID",
+          "name": "id",
+          "required": true
+        },
+        "value": {
+          "description": "variable value; if omitted, use value from this process' environment",
+          "name": "value",
           "required": true
         }
       },
-      "description": "Identify a device.\n\nIdentify a device by making the ACT LED blink (Raspberry Pi).",
+      "description": "Change the value of a config or env var for a fleet, device or service.\n\nChange the value of a configuration or environment variable for a fleet,\ndevice or service, as selected by command-line options.\n\nVariables are selected by their database ID (as reported by the 'balena env list'\ncommand) and one of six database \"resource types\":\n\n- fleet environment variable\n- fleet configuration variable (--config)\n- fleet service variable (--service)\n- device environment variable (--device)\n- device configuration variable (--device --config)\n- device service variable (--device --service)\n\nThe --device option selects a device-specific variable instead of a fleet\nvariable.\n\nThe --config option selects a configuration variable. Configuration variable\nnames typically start with the 'BALENA_' or 'RESIN_' prefixes and are used to\nconfigure balena platform features.\n\nThe --service option selects a service variable, which is an environment variable\nthat applies to a specifc service (container) in a microservices (multicontainer)\nfleet.\n\nThe --service and --config options cannot be used together, but they can be\nused alongside the --device option to select a device-specific service or\nconfiguration variable.",
       "examples": [
-        "$ balena device identify 23c73a1"
+        "$ balena env rename 123123 emacs",
+        "$ balena env rename 234234 emacs --service",
+        "$ balena env rename 345345 emacs --device",
+        "$ balena env rename 456456 emacs --device --service",
+        "$ balena env rename 567567 1 --config",
+        "$ balena env rename 678678 1 --device --config"
       ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "device:identify",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
+      "flags": {
+        "config": {
+          "char": "c",
+          "description": "select a configuration variable (may be used together with the --device option)",
+          "exclusive": [
+            "service"
+          ],
+          "name": "config",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "device": {
+          "char": "d",
+          "description": "select a device-specific variable instead of a fleet variable",
+          "name": "device",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "service": {
+          "char": "s",
+          "description": "select a service variable (may be used together with the --device option)",
+          "exclusive": [
+            "config"
+          ],
+          "name": "service",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "env:rename",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "device",
-        "identify.js"
+        "env",
+        "rename.js"
       ]
     },
-    "device": {
+    "env:rm": {
       "aliases": [],
       "args": {
-        "uuid": {
-          "description": "the device uuid",
-          "name": "uuid",
+        "id": {
+          "description": "variable's numeric database ID",
+          "name": "id",
           "required": true
         }
       },
-      "description": "Show info about a single device.\n\nShow information about a single device.",
+      "description": "Remove a config or env var from a fleet, device or service.\n\nRemove a configuration or environment variable from a fleet, device\nor service, as selected by command-line options.\n\nVariables are selected by their database ID (as reported by the 'balena env list'\ncommand) and one of six database \"resource types\":\n\n- fleet environment variable\n- fleet configuration variable (--config)\n- fleet service variable (--service)\n- device environment variable (--device)\n- device configuration variable (--device --config)\n- device service variable (--device --service)\n\nThe --device option selects a device-specific variable instead of a fleet\nvariable.\n\nThe --config option selects a configuration variable. Configuration variable\nnames typically start with the 'BALENA_' or 'RESIN_' prefixes and are used to\nconfigure balena platform features.\n\nThe --service option selects a service variable, which is an environment variable\nthat applies to a specifc service (container) in a microservices (multicontainer)\nfleet.\n\nThe --service and --config options cannot be used together, but they can be\nused alongside the --device option to select a device-specific service or\nconfiguration variable.\n\nInteractive confirmation is normally asked before the variable is deleted.\nThe --yes option disables this behavior.",
       "examples": [
-        "$ balena device 7cf02a6",
-        "$ balena device 7cf02a6 --view"
+        "$ balena env rm 123123",
+        "$ balena env rm 234234 --yes",
+        "$ balena env rm 345345 --config",
+        "$ balena env rm 456456 --service",
+        "$ balena env rm 567567 --device",
+        "$ balena env rm 678678 --device --config",
+        "$ balena env rm 789789 --device --service --yes"
       ],
       "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
+        "config": {
+          "char": "c",
+          "description": "select a configuration variable (may be used together with the --device option)",
+          "exclusive": [
+            "service"
+          ],
+          "name": "config",
           "allowNo": false,
           "type": "boolean"
         },
-        "view": {
-          "description": "open device dashboard page",
-          "name": "view",
+        "device": {
+          "char": "d",
+          "description": "select a device-specific variable instead of a fleet variable",
+          "name": "device",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "service": {
+          "char": "s",
+          "description": "select a service variable (may be used together with the --device option)",
+          "exclusive": [
+            "config"
+          ],
+          "name": "service",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "yes": {
+          "char": "y",
+          "description": "do not prompt for confirmation before deleting the variable",
+          "name": "yes",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "device",
+      "id": "env:rm",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
-      "enableJsonFlag": true,
-      "authenticated": true,
-      "primary": true,
+      "enableJsonFlag": false,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "device",
-        "index.js"
+        "env",
+        "rm.js"
       ]
     },
-    "device:init": {
+    "env:set": {
       "aliases": [],
-      "args": {},
-      "description": "Initialize a device with balenaOS.\n\nRegister a new device in the selected fleet, download the OS image for the\nfleet's default device type, configure the image and write it to an SD card.\nThis command effectively combines several other balena CLI commands in one,\nnamely:\n\n'balena device register'\n'balena os download'\n'balena config generate'\n'balena os configure'\n'balena os local flash'\n\nPossible arguments for the '--fleet', '--os-version' and '--drive' options can\nbe listed respectively with the commands:\n\n'balena fleet list'\n'balena os versions'\n'balena util available-drives'\n\nIf the '--fleet' or '--drive' options are omitted, interactive menus will be\npresented with values to choose from. If the '--os-version' option is omitted,\nthe latest released OS version for the fleet's default device type will be used.\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\nImage configuration questions will be asked interactively unless a pre-configured\n'config.json' file is provided with the '--config' option.  The file can be\ngenerated with the 'balena config generate' command.",
+      "args": {
+        "name": {
+          "description": "environment or config variable name",
+          "name": "name",
+          "required": true
+        },
+        "value": {
+          "description": "variable value; if omitted, use value from this process' environment",
+          "name": "value",
+          "required": false
+        }
+      },
+      "description": "Add or update env or config variable to fleets, devices or services.\n\nAdd or update an environment or config variable to one or more fleets, devices or\nservices, as selected by the respective command-line options. Either the\n--fleet or the --device option must be provided,  and either may be be\nused alongside the --service option to define a service-specific variable.\n(A service corresponds to a Docker image/container in a microservices fleet.)\nWhen the --service option is used in conjunction with the --device option,\nthe service variable applies to the selected device only.  Otherwise, it\napplies to all devices of the selected fleet. If the --service option is\nomitted, the variable applies to all services.\n\nIf VALUE is omitted, the CLI will attempt to use the value of the environment\nvariable of same name in the CLI process' environment. In this case, a warning\nmessage will be printed. Use `--quiet` to suppress it.\n\n'BALENA_' or 'RESIN_' are reserved variable name prefixes used to identify\n\"configuration variables\". Configuration variables control balena platform\nfeatures and are treated specially by balenaOS and the balena supervisor\nrunning on devices. They are also stored differently in the balenaCloud API\ndatabase. Configuration variables cannot be set for specific services,\ntherefore the --service option cannot be used when the variable name starts\nwith a reserved prefix. When defining custom fleet variables, please avoid\nthese reserved prefixes.\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 device init",
-        "$ balena device init -f myorg/myfleet",
-        "$ balena device init --fleet myFleet --os-version 2.101.7 --drive /dev/disk5",
-        "$ balena device init --fleet myFleet --os-version 2.83.21+rev1.prod --drive /dev/disk5",
-        "$ balena device init --config config.json --os-version 2.101.7 --drive /dev/disk5 --yes"
+        "$ balena env set TERM --fleet MyFleet",
+        "$ balena env set EDITOR vim -f myorg/myfleet",
+        "$ balena env set EDITOR vim --fleet MyFleet,MyFleet2",
+        "$ balena env set EDITOR vim --fleet MyFleet --service MyService",
+        "$ balena env set EDITOR vim --fleet MyFleet,MyFleet2 --service MyService,MyService2",
+        "$ balena env set EDITOR vim --device 7cf02a6",
+        "$ balena env set EDITOR vim --device 7cf02a6,d6f1433",
+        "$ balena env set EDITOR vim --device 7cf02a6 --service MyService",
+        "$ balena env set EDITOR vim --device 7cf02a6,d6f1433 --service MyService,MyService2"
       ],
       "flags": {
         "fleet": {
           "char": "f",
           "description": "fleet name or slug (preferred)",
           "exclusive": [
-            "config"
+            "device"
           ],
           "name": "fleet",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "config": {
-          "description": "path to the config JSON file, see `balena config generate`",
+        "device": {
+          "char": "d",
+          "description": "device UUID",
           "exclusive": [
-            "fleet",
-            "advanced",
-            "provisioning-key-name",
-            "provisioning-key-expiry-date"
+            "fleet"
           ],
-          "name": "config",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "os-version": {
-          "description": "exact version number, or a valid semver range,\nor 'latest' (includes pre-releases),\nor 'default' (excludes pre-releases if at least one stable version is available),\nor 'recommended' (excludes pre-releases, will fail if only pre-release versions are available),\nor 'menu' (will show the interactive menu)",
-          "name": "os-version",
+          "name": "device",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "advanced": {
-          "char": "v",
-          "description": "show advanced configuration options",
-          "name": "advanced",
+        "quiet": {
+          "char": "q",
+          "description": "suppress warning messages",
+          "name": "quiet",
           "allowNo": false,
           "type": "boolean"
         },
-        "provisioning-key-name": {
-          "description": "custom key name assigned to generated provisioning api key",
-          "name": "provisioning-key-name",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "provisioning-key-expiry-date": {
-          "description": "expiry date assigned to generated provisioning api key (format: YYYY-MM-DD)",
-          "name": "provisioning-key-expiry-date",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "drive": {
-          "char": "d",
-          "description": "the drive to write the image to, eg. `/dev/sdb` or `/dev/mmcblk0`.\nCareful with this as you can erase your hard drive.\nCheck `balena util available-drives` for available options.",
-          "name": "drive",
+        "service": {
+          "char": "s",
+          "description": "service name",
+          "name": "service",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
-        },
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "env:set",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": false,
+      "enableJsonFlag": false,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "env",
+        "set.js"
+      ]
+    },
+    "device:deactivate": {
+      "aliases": [],
+      "args": {
+        "uuid": {
+          "description": "the UUID of the device to be deactivated",
+          "name": "uuid",
+          "required": true
+        }
+      },
+      "description": "Deactivate a device.\n\nDeactivate a device.\n\nNote this command asks for confirmation interactively.\nYou can avoid this by passing the `--yes` option.",
+      "examples": [
+        "$ balena device deactivate 7cf02a6",
+        "$ balena device deactivate 7cf02a6 --yes"
+      ],
+      "flags": {
         "yes": {
           "char": "y",
           "description": "answer \"yes\" to all questions (non interactive use)",
@@ -1288,7 +1342,7 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "device:init",
+      "id": "device:deactivate",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -1300,17 +1354,17 @@
         "build",
         "commands",
         "device",
-        "init.js"
+        "deactivate.js"
       ]
     },
-    "device:list": {
+    "device:detect": {
       "aliases": [],
       "args": {},
-      "description": "List all devices.\n\nList all of your devices.\n\nDevices can be filtered by fleet with the `--fleet` option.\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": "Scan for balenaOS devices on your local network.\n\nScan for balenaOS devices on your local network.\n\nThe output includes device information collected through balenaEngine for\ndevices running a development image of balenaOS. Devices running a production\nimage do not expose balenaEngine (on TCP port 2375), which is why less\ninformation is printed about them.",
       "examples": [
-        "$ balena device list",
-        "$ balena device list --fleet MyFleet",
-        "$ balena device list -f myorg/myfleet"
+        "$ balena device detect",
+        "$ balena device detect --timeout 120",
+        "$ balena device detect --verbose"
       ],
       "flags": {
         "json": {
@@ -1320,10 +1374,17 @@
           "allowNo": false,
           "type": "boolean"
         },
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
+        "verbose": {
+          "char": "v",
+          "description": "display full info",
+          "name": "verbose",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "timeout": {
+          "char": "t",
+          "description": "scan timeout in seconds",
+          "name": "timeout",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -1331,16 +1392,254 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "device:list",
+      "id": "device:detect",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": true,
       "primary": true,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
+      "root": true,
+      "offlineCompatible": true,
+      "dockerInfoProperties": [
+        "Containers",
+        "ContainersRunning",
+        "ContainersPaused",
+        "ContainersStopped",
+        "Images",
+        "Driver",
+        "SystemTime",
+        "KernelVersion",
+        "OperatingSystem",
+        "Architecture"
+      ],
+      "dockerVersionProperties": [
+        "Version",
+        "ApiVersion"
+      ],
+      "noDevicesFoundMessage": "Could not find any balenaOS devices on the local network.",
+      "windowsTipMessage": "\n\nNote for Windows users:\n  The 'device detect' command relies on the Bonjour service. Check whether Bonjour is\n  installed (Control Panel > Programs and Features). If not, you can download\n  Bonjour for Windows (included with Bonjour Print Services) from here:\n  https://support.apple.com/kb/DL999\n\n  After installing Bonjour, restart your PC and run the 'balena device detect' command\n  again.",
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "device",
+        "detect.js"
+      ]
+    },
+    "device:identify": {
+      "aliases": [],
+      "args": {
+        "uuid": {
+          "description": "the uuid of the device to identify",
+          "name": "uuid",
+          "required": true
+        }
+      },
+      "description": "Identify a device.\n\nIdentify a device by making the ACT LED blink (Raspberry Pi).",
+      "examples": [
+        "$ balena device identify 23c73a1"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "device:identify",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "device",
+        "identify.js"
+      ]
+    },
+    "device": {
+      "aliases": [],
+      "args": {
+        "uuid": {
+          "description": "the device uuid",
+          "name": "uuid",
+          "required": true
+        }
+      },
+      "description": "Show info about a single device.\n\nShow information about a single device.",
+      "examples": [
+        "$ balena device 7cf02a6",
+        "$ balena device 7cf02a6 --view"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "view": {
+          "description": "open device dashboard page",
+          "name": "view",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "device",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": true,
+      "authenticated": true,
+      "primary": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "device",
+        "index.js"
+      ]
+    },
+    "device:init": {
+      "aliases": [],
+      "args": {},
+      "description": "Initialize a device with balenaOS.\n\nRegister a new device in the selected fleet, download the OS image for the\nfleet's default device type, configure the image and write it to an SD card.\nThis command effectively combines several other balena CLI commands in one,\nnamely:\n\n'balena device register'\n'balena os download'\n'balena config generate'\n'balena os configure'\n'balena os local flash'\n\nPossible arguments for the '--fleet', '--os-version' and '--drive' options can\nbe listed respectively with the commands:\n\n'balena fleet list'\n'balena os versions'\n'balena util available-drives'\n\nIf the '--fleet' or '--drive' options are omitted, interactive menus will be\npresented with values to choose from. If the '--os-version' option is omitted,\nthe latest released OS version for the fleet's default device type will be used.\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\nImage configuration questions will be asked interactively unless a pre-configured\n'config.json' file is provided with the '--config' option.  The file can be\ngenerated with the 'balena config generate' command.",
+      "examples": [
+        "$ balena device init",
+        "$ balena device init -f myorg/myfleet",
+        "$ balena device init --fleet myFleet --os-version 2.101.7 --drive /dev/disk5",
+        "$ balena device init --fleet myFleet --os-version 2.83.21+rev1.prod --drive /dev/disk5",
+        "$ balena device init --config config.json --os-version 2.101.7 --drive /dev/disk5 --yes"
+      ],
+      "flags": {
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "exclusive": [
+            "config"
+          ],
+          "name": "fleet",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "config": {
+          "description": "path to the config JSON file, see `balena config generate`",
+          "exclusive": [
+            "fleet",
+            "advanced",
+            "provisioning-key-name",
+            "provisioning-key-expiry-date"
+          ],
+          "name": "config",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "os-version": {
+          "description": "exact version number, or a valid semver range,\nor 'latest' (includes pre-releases),\nor 'default' (excludes pre-releases if at least one stable version is available),\nor 'recommended' (excludes pre-releases, will fail if only pre-release versions are available),\nor 'menu' (will show the interactive menu)",
+          "name": "os-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "advanced": {
+          "char": "v",
+          "description": "show advanced configuration options",
+          "name": "advanced",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "provisioning-key-name": {
+          "description": "custom key name assigned to generated provisioning api key",
+          "name": "provisioning-key-name",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "provisioning-key-expiry-date": {
+          "description": "expiry date assigned to generated provisioning api key (format: YYYY-MM-DD)",
+          "name": "provisioning-key-expiry-date",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "drive": {
+          "char": "d",
+          "description": "the drive to write the image to, eg. `/dev/sdb` or `/dev/mmcblk0`.\nCareful with this as you can erase your hard drive.\nCheck `balena util available-drives` for available options.",
+          "name": "drive",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "yes": {
+          "char": "y",
+          "description": "answer \"yes\" to all questions (non interactive use)",
+          "name": "yes",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "device:init",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "device",
+        "init.js"
+      ]
+    },
+    "device:list": {
+      "aliases": [],
+      "args": {},
+      "description": "List all devices.\n\nList all of your devices.\n\nDevices can be filtered by fleet with the `--fleet` option.\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 device list",
+        "$ balena device list --fleet MyFleet",
+        "$ balena device list -f myorg/myfleet"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "name": "fleet",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "device:list",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": true,
+      "primary": true,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
         "build",
         "commands",
         "device",
@@ -2195,346 +2494,47 @@
       },
       "description": "Tunnel local ports to your balenaOS device.\n\nUse this command to open local TCP ports that tunnel to listening sockets in a\nbalenaOS device.\n\nFor example, this command could be used to expose the ssh server of a balenaOS\ndevice (port number 22222) on the local machine, or to expose a web server\nrunning on the device. The port numbers do not have be the same between the\ndevice and the local machine, and multiple ports may be tunneled in a single\ncommand line.\n\nPort mappings are specified in the format: <remotePort>[:[localIP:]localPort]\nlocalIP defaults to 'localhost', and localPort defaults to the specified\nremotePort value.\n\nNote: the -p (--port) flag must be provided at the end of the command line,\nas per examples.\n\nIn the case of openBalena, the tunnel command in CLI v12.38.5 or later requires\nopenBalena v3.1.2 or later. Older CLI versions work with older openBalena\nversions.",
       "examples": [
-        "# map remote port 22222 to localhost:22222",
-        "$ balena device tunnel myFleet -p 22222",
-        "",
-        "# map remote port 22222 to localhost:222",
-        "$ balena device tunnel 2ead211 -p 22222:222",
-        "",
-        "# map remote port 22222 to any address on your host machine, port 22222",
-        "$ balena device tunnel 1546690 -p 22222:0.0.0.0",
-        "",
-        "# map remote port 22222 to any address on your host machine, port 222",
-        "$ balena device tunnel myFleet -p 22222:0.0.0.0:222",
-        "",
-        "# multiple port tunnels can be specified at any one time",
-        "$ balena device tunnel myFleet -p 8080:3000 -p 8081:9000"
-      ],
-      "flags": {
-        "port": {
-          "char": "p",
-          "description": "port mapping in the format <remotePort>[:[localIP:]localPort]",
-          "name": "port",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "device:tunnel",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "primary": true,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "device",
-        "tunnel.js"
-      ]
-    },
-    "env:list": {
-      "aliases": [],
-      "args": {},
-      "description": "List the environment or config variables of a fleet, device or service.\n\nList the environment or configuration variables of a fleet, device or\nservice, as selected by the respective command-line options. (A service\ncorresponds to a Docker image/container in a microservices fleet.)\n\nThe results include fleet-wide (multiple devices), device-specific (multiple\nservices on a specific device) and service-specific variables that apply to the\nselected fleet, device or service. It can be thought of as including inherited\nvariables; for example, a service inherits device-wide variables, and a device\ninherits fleet-wide variables.\n\nThe printed output may include DEVICE and/or SERVICE columns to distinguish\nbetween fleet-wide, device-specific and service-specific variables.\nAn asterisk in these columns indicates that the variable applies to\n\"all devices\" or \"all services\".\n\nThe --config option is used to list \"configuration variables\" that control\nbalena platform features, as opposed to custom environment variables defined\nby the user. The --config and the --service options are mutually exclusive\nbecause configuration variables cannot be set for specific services.\n\nWhen --json is used, an empty JSON array ([]) is printed instead of an error \nmessage when no variables exist for the given query. When querying variables \nfor a device, note that the fleet name may be null in JSON output \n(or 'N/A' in tabular output) if the fleet that the device belonged to is no \nlonger accessible by the current user (for example, in case the current user \nwas removed from the fleet by the fleet's owner).\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 env list --fleet myorg/myfleet",
-        "$ balena env list --fleet MyFleet --service MyService",
-        "$ balena env list --fleet MyFleet --config",
-        "$ balena env list --device 7cf02a6",
-        "$ balena env list --device 7cf02a6 --service MyService"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "exclusive": [
-            "device"
-          ],
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "config": {
-          "char": "c",
-          "description": "show configuration variables only",
-          "exclusive": [
-            "service"
-          ],
-          "name": "config",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "device": {
-          "char": "d",
-          "description": "device UUID",
-          "exclusive": [
-            "fleet"
-          ],
-          "name": "device",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "service": {
-          "char": "s",
-          "description": "service name",
-          "exclusive": [
-            "config"
-          ],
-          "name": "service",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "env:list",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "env",
-        "list.js"
-      ]
-    },
-    "env:rename": {
-      "aliases": [],
-      "args": {
-        "id": {
-          "description": "variable's numeric database ID",
-          "name": "id",
-          "required": true
-        },
-        "value": {
-          "description": "variable value; if omitted, use value from this process' environment",
-          "name": "value",
-          "required": true
-        }
-      },
-      "description": "Change the value of a config or env var for a fleet, device or service.\n\nChange the value of a configuration or environment variable for a fleet,\ndevice or service, as selected by command-line options.\n\nVariables are selected by their database ID (as reported by the 'balena env list'\ncommand) and one of six database \"resource types\":\n\n- fleet environment variable\n- fleet configuration variable (--config)\n- fleet service variable (--service)\n- device environment variable (--device)\n- device configuration variable (--device --config)\n- device service variable (--device --service)\n\nThe --device option selects a device-specific variable instead of a fleet\nvariable.\n\nThe --config option selects a configuration variable. Configuration variable\nnames typically start with the 'BALENA_' or 'RESIN_' prefixes and are used to\nconfigure balena platform features.\n\nThe --service option selects a service variable, which is an environment variable\nthat applies to a specifc service (container) in a microservices (multicontainer)\nfleet.\n\nThe --service and --config options cannot be used together, but they can be\nused alongside the --device option to select a device-specific service or\nconfiguration variable.",
-      "examples": [
-        "$ balena env rename 123123 emacs",
-        "$ balena env rename 234234 emacs --service",
-        "$ balena env rename 345345 emacs --device",
-        "$ balena env rename 456456 emacs --device --service",
-        "$ balena env rename 567567 1 --config",
-        "$ balena env rename 678678 1 --device --config"
-      ],
-      "flags": {
-        "config": {
-          "char": "c",
-          "description": "select a configuration variable (may be used together with the --device option)",
-          "exclusive": [
-            "service"
-          ],
-          "name": "config",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "device": {
-          "char": "d",
-          "description": "select a device-specific variable instead of a fleet variable",
-          "name": "device",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "service": {
-          "char": "s",
-          "description": "select a service variable (may be used together with the --device option)",
-          "exclusive": [
-            "config"
-          ],
-          "name": "service",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "env:rename",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "env",
-        "rename.js"
-      ]
-    },
-    "env:rm": {
-      "aliases": [],
-      "args": {
-        "id": {
-          "description": "variable's numeric database ID",
-          "name": "id",
-          "required": true
-        }
-      },
-      "description": "Remove a config or env var from a fleet, device or service.\n\nRemove a configuration or environment variable from a fleet, device\nor service, as selected by command-line options.\n\nVariables are selected by their database ID (as reported by the 'balena env list'\ncommand) and one of six database \"resource types\":\n\n- fleet environment variable\n- fleet configuration variable (--config)\n- fleet service variable (--service)\n- device environment variable (--device)\n- device configuration variable (--device --config)\n- device service variable (--device --service)\n\nThe --device option selects a device-specific variable instead of a fleet\nvariable.\n\nThe --config option selects a configuration variable. Configuration variable\nnames typically start with the 'BALENA_' or 'RESIN_' prefixes and are used to\nconfigure balena platform features.\n\nThe --service option selects a service variable, which is an environment variable\nthat applies to a specifc service (container) in a microservices (multicontainer)\nfleet.\n\nThe --service and --config options cannot be used together, but they can be\nused alongside the --device option to select a device-specific service or\nconfiguration variable.\n\nInteractive confirmation is normally asked before the variable is deleted.\nThe --yes option disables this behavior.",
-      "examples": [
-        "$ balena env rm 123123",
-        "$ balena env rm 234234 --yes",
-        "$ balena env rm 345345 --config",
-        "$ balena env rm 456456 --service",
-        "$ balena env rm 567567 --device",
-        "$ balena env rm 678678 --device --config",
-        "$ balena env rm 789789 --device --service --yes"
-      ],
-      "flags": {
-        "config": {
-          "char": "c",
-          "description": "select a configuration variable (may be used together with the --device option)",
-          "exclusive": [
-            "service"
-          ],
-          "name": "config",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "device": {
-          "char": "d",
-          "description": "select a device-specific variable instead of a fleet variable",
-          "name": "device",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "service": {
-          "char": "s",
-          "description": "select a service variable (may be used together with the --device option)",
-          "exclusive": [
-            "config"
-          ],
-          "name": "service",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "yes": {
-          "char": "y",
-          "description": "do not prompt for confirmation before deleting the variable",
-          "name": "yes",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "env:rm",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "env",
-        "rm.js"
-      ]
-    },
-    "env:set": {
-      "aliases": [],
-      "args": {
-        "name": {
-          "description": "environment or config variable name",
-          "name": "name",
-          "required": true
-        },
-        "value": {
-          "description": "variable value; if omitted, use value from this process' environment",
-          "name": "value",
-          "required": false
-        }
-      },
-      "description": "Add or update env or config variable to fleets, devices or services.\n\nAdd or update an environment or config variable to one or more fleets, devices or\nservices, as selected by the respective command-line options. Either the\n--fleet or the --device option must be provided,  and either may be be\nused alongside the --service option to define a service-specific variable.\n(A service corresponds to a Docker image/container in a microservices fleet.)\nWhen the --service option is used in conjunction with the --device option,\nthe service variable applies to the selected device only.  Otherwise, it\napplies to all devices of the selected fleet. If the --service option is\nomitted, the variable applies to all services.\n\nIf VALUE is omitted, the CLI will attempt to use the value of the environment\nvariable of same name in the CLI process' environment. In this case, a warning\nmessage will be printed. Use `--quiet` to suppress it.\n\n'BALENA_' or 'RESIN_' are reserved variable name prefixes used to identify\n\"configuration variables\". Configuration variables control balena platform\nfeatures and are treated specially by balenaOS and the balena supervisor\nrunning on devices. They are also stored differently in the balenaCloud API\ndatabase. Configuration variables cannot be set for specific services,\ntherefore the --service option cannot be used when the variable name starts\nwith a reserved prefix. When defining custom fleet variables, please avoid\nthese reserved prefixes.\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 env set TERM --fleet MyFleet",
-        "$ balena env set EDITOR vim -f myorg/myfleet",
-        "$ balena env set EDITOR vim --fleet MyFleet,MyFleet2",
-        "$ balena env set EDITOR vim --fleet MyFleet --service MyService",
-        "$ balena env set EDITOR vim --fleet MyFleet,MyFleet2 --service MyService,MyService2",
-        "$ balena env set EDITOR vim --device 7cf02a6",
-        "$ balena env set EDITOR vim --device 7cf02a6,d6f1433",
-        "$ balena env set EDITOR vim --device 7cf02a6 --service MyService",
-        "$ balena env set EDITOR vim --device 7cf02a6,d6f1433 --service MyService,MyService2"
+        "# map remote port 22222 to localhost:22222",
+        "$ balena device tunnel myFleet -p 22222",
+        "",
+        "# map remote port 22222 to localhost:222",
+        "$ balena device tunnel 2ead211 -p 22222:222",
+        "",
+        "# map remote port 22222 to any address on your host machine, port 22222",
+        "$ balena device tunnel 1546690 -p 22222:0.0.0.0",
+        "",
+        "# map remote port 22222 to any address on your host machine, port 222",
+        "$ balena device tunnel myFleet -p 22222:0.0.0.0:222",
+        "",
+        "# multiple port tunnels can be specified at any one time",
+        "$ balena device tunnel myFleet -p 8080:3000 -p 8081:9000"
       ],
       "flags": {
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "exclusive": [
-            "device"
-          ],
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "device": {
-          "char": "d",
-          "description": "device UUID",
-          "exclusive": [
-            "fleet"
-          ],
-          "name": "device",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "quiet": {
-          "char": "q",
-          "description": "suppress warning messages",
-          "name": "quiet",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "service": {
-          "char": "s",
-          "description": "service name",
-          "name": "service",
+        "port": {
+          "char": "p",
+          "description": "port mapping in the format <remotePort>[:[localIP:]localPort]",
+          "name": "port",
           "hasDynamicHelp": false,
-          "multiple": false,
+          "multiple": true,
           "type": "option"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "env:set",
+      "id": "device:tunnel",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
-      "strict": false,
+      "strict": true,
       "enableJsonFlag": false,
+      "primary": true,
+      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "env",
-        "set.js"
+        "device",
+        "tunnel.js"
       ]
     },
     "fleet:create": {
@@ -3837,241 +3837,59 @@
           "hasDynamicHelp": false,
           "multiple": true,
           "type": "option"
-        },
-        "noconvert-eol": {
-          "description": "Don't convert line endings from CRLF (Windows format) to LF (Unix format).",
-          "name": "noconvert-eol",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "multi-dockerignore": {
-          "char": "m",
-          "description": "Have each service use its own .dockerignore file. See \"balena help push\".",
-          "name": "multi-dockerignore",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "release-tag": {
-          "description": "Set release tags if the image build is successful (balenaCloud only). Multiple\narguments may be provided, alternating tag keys and values (see examples).\nHint: Empty values may be specified with \"\" (bash, cmd.exe) or '\"\"' (PowerShell).",
-          "exclusive": [
-            "detached"
-          ],
-          "name": "release-tag",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "draft": {
-          "description": "Instruct the builder to create the release as a draft. Draft releases are ignored\nby the 'track latest' release policy but can be used through release pinning.\nDraft releases can be marked as final through the API. Releases are created\nas final by default unless this option is given.",
-          "name": "draft",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "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",
+        },
+        "noconvert-eol": {
+          "description": "Don't convert line endings from CRLF (Windows format) to LF (Unix format).",
+          "name": "noconvert-eol",
           "allowNo": false,
           "type": "boolean"
+        },
+        "multi-dockerignore": {
+          "char": "m",
+          "description": "Have each service use its own .dockerignore file. See \"balena help push\".",
+          "name": "multi-dockerignore",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "release-tag": {
+          "description": "Set release tags if the image build is successful (balenaCloud only). Multiple\narguments may be provided, alternating tag keys and values (see examples).\nHint: Empty values may be specified with \"\" (bash, cmd.exe) or '\"\"' (PowerShell).",
+          "exclusive": [
+            "detached"
+          ],
+          "name": "release-tag",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "draft": {
+          "description": "Instruct the builder to create the release as a draft. Draft releases are ignored\nby the 'track latest' release policy but can be used through release pinning.\nDraft releases can be marked as final through the API. Releases are created\nas final by default unless this option is given.",
+          "name": "draft",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "note": {
+          "description": "The notes for this release",
+          "name": "note",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         }
       },
       "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",
+      "id": "push",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "authenticated": true,
+      "primary": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "release",
-        "validate.js"
+        "push",
+        "index.js"
       ]
     },
     "release-asset:delete": {
@@ -4289,6 +4107,188 @@
         "upload.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": "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"
+      ]
+    },
     "settings": {
       "aliases": [],
       "args": {},
@@ -4777,5 +4777,5 @@
       ]
     }
   },
-  "version": "23.2.14"
+  "version": "23.2.15"
 }