balena-cli 23.2.12 → 23.2.13-build-update-docker-progress-5-4-0-11745cd340eeb2790888818f755922221cd78df9-1

package/oclif.manifest.json

@@ -160,56 +160,6 @@
         "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": {
@@ -412,6 +362,56 @@
         "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,16 +1018,54 @@
         "list.js"
       ]
     },
-    "env:list": {
+    "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": {
       "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).",
+      "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 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"
+        "$ balena device detect",
+        "$ balena device detect --timeout 120",
+        "$ balena device detect --verbose"
       ],
       "flags": {
         "json": {
@@ -1037,45 +1075,17 @@
           "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",
+        "verbose": {
+          "char": "v",
+          "description": "display full info",
+          "name": "verbose",
           "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",
+        "timeout": {
+          "char": "t",
+          "description": "scan timeout in seconds",
+          "name": "timeout",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -1083,362 +1093,53 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "env:list",
+      "id": "device:detect",
       "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",
-        "env",
-        "list.js"
+        "device",
+        "detect.js"
       ]
     },
-    "env:rename": {
+    "device:identify": {
       "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",
+        "uuid": {
+          "description": "the uuid of the device to identify",
+          "name": "uuid",
           "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.",
+      "description": "Identify a device.\n\nIdentify a device by making the ACT LED blink (Raspberry Pi).",
       "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"
-      ],
-      "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",
-          "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)",
-          "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": {
-      "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.",
-      "examples": [
-        "$ balena device detect",
-        "$ balena device detect --timeout 120",
-        "$ balena device detect --verbose"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "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"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "device:detect",
-      "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"
-      ]
-    },
-    "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"
+        "$ balena device identify 23c73a1"
       ],
       "flags": {},
       "hasDynamicHelp": false,
@@ -2461,80 +2162,379 @@
           "required": true
         }
       },
-      "description": "Make a device track the fleet's pinned release.\n\nMake a device track the fleet's pinned release.",
-      "examples": [
-        "$ balena device track-fleet 7cf02a6"
-      ],
-      "flags": {},
+      "description": "Make a device track the fleet's pinned release.\n\nMake a device track the fleet's pinned release.",
+      "examples": [
+        "$ balena device track-fleet 7cf02a6"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "device:track-fleet",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "device",
+        "track-fleet.js"
+      ]
+    },
+    "device:tunnel": {
+      "aliases": [],
+      "args": {
+        "deviceOrFleet": {
+          "description": "device UUID or fleet name/slug",
+          "name": "deviceOrFleet",
+          "required": true
+        }
+      },
+      "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": "device:track-fleet",
+      "id": "env:rm",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "device",
-        "track-fleet.js"
+        "env",
+        "rm.js"
       ]
     },
-    "device:tunnel": {
+    "env:set": {
       "aliases": [],
       "args": {
-        "deviceOrFleet": {
-          "description": "device UUID or fleet name/slug",
-          "name": "deviceOrFleet",
+        "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": "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.",
+      "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": [
-        "# 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"
+        "$ 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": {
-        "port": {
-          "char": "p",
-          "description": "port mapping in the format <remotePort>[:[localIP:]localPort]",
-          "name": "port",
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "exclusive": [
+            "device"
+          ],
+          "name": "fleet",
           "hasDynamicHelp": false,
-          "multiple": true,
+          "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",
+          "hasDynamicHelp": false,
+          "multiple": false,
           "type": "option"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "device:tunnel",
+      "id": "env:set",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
-      "strict": true,
+      "strict": false,
       "enableJsonFlag": false,
-      "primary": true,
-      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "device",
-        "tunnel.js"
+        "env",
+        "set.js"
       ]
     },
     "fleet:create": {
@@ -2916,172 +2916,57 @@
         "osinit.js"
       ]
     },
-    "leave": {
-      "aliases": [],
-      "args": {
-        "deviceIpOrHostname": {
-          "description": "the device IP or hostname",
-          "name": "deviceIpOrHostname"
-        }
-      },
-      "description": "Remove a local device from its balena fleet.\n\nRemove a local device from its balena fleet, causing the device to\n\"leave\" the server it is provisioned on. This effectively makes the device\n\"unmanaged\". The device must be running balenaOS.\n\nThe device entry on the server is preserved after running this command,\nso the device can subsequently re-join the server if needed.\n\nIf you don't specify a device hostname or IP, this command will automatically\nscan the local network for balenaOS devices and prompt you to select one\nfrom an interactive picker. This may require administrator/root privileges.",
-      "examples": [
-        "$ balena leave",
-        "$ balena leave balena.local",
-        "$ balena leave 192.168.1.25"
-      ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "leave",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "primary": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "leave",
-        "index.js"
-      ]
-    },
-    "join": {
-      "aliases": [],
-      "args": {
-        "deviceIpOrHostname": {
-          "description": "the IP or hostname of device",
-          "name": "deviceIpOrHostname"
-        }
-      },
-      "description": "Move a local device to a fleet on another balena server.\n\nMove a local device to a fleet on another balena server, causing\nthe device to \"join\" the new server. The device must be running balenaOS.\n\nFor example, you could provision a device against an openBalena installation\nwhere you perform end-to-end tests and then move it to balenaCloud when it's\nready for production.\n\nTo move a device between fleets on the same server, use the\n`balena device move` command instead of `balena join`.\n\nIf you don't specify a device hostname or IP, this command will automatically\nscan the local network for balenaOS devices and prompt you to select one\nfrom an interactive picker. This may require administrator/root privileges.\nLikewise, if the fleet option is not provided then a picker will be shown.\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 join",
-        "$ balena join balena.local",
-        "$ balena join balena.local --fleet MyFleet",
-        "$ balena join balena.local -f myorg/myfleet",
-        "$ balena join 192.168.1.25",
-        "$ balena join 192.168.1.25 --fleet MyFleet"
-      ],
-      "flags": {
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "pollInterval": {
-          "char": "i",
-          "description": "the interval in minutes to check for updates",
-          "name": "pollInterval",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "join",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "primary": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "join",
-        "index.js"
-      ]
-    },
-    "local:configure": {
-      "aliases": [],
-      "args": {
-        "target": {
-          "description": "path of drive or image to configure",
-          "name": "target",
-          "required": true
-        }
-      },
-      "description": "(Re)configure a balenaOS drive or image.\n\nConfigure or reconfigure a balenaOS drive or image.",
-      "examples": [
-        "$ balena local configure /dev/sdc",
-        "$ balena local configure path/to/image.img"
-      ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "local:configure",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "root": true,
-      "offlineCompatible": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "local",
-        "configure.js"
-      ]
-    },
-    "local:flash": {
+    "join": {
       "aliases": [],
       "args": {
-        "image": {
-          "description": "path to OS image",
-          "name": "image",
-          "required": true
+        "deviceIpOrHostname": {
+          "description": "the IP or hostname of device",
+          "name": "deviceIpOrHostname"
         }
       },
-      "description": "Flash an image to a drive.\n\nFlash a balenaOS image to a drive.\nImage file may be one of: .img|.zip|.gz|.bz2|.xz\n\nIf --drive is not specified, then it will interactively\nshow a list of available drives for selection.",
+      "description": "Move a local device to a fleet on another balena server.\n\nMove a local device to a fleet on another balena server, causing\nthe device to \"join\" the new server. The device must be running balenaOS.\n\nFor example, you could provision a device against an openBalena installation\nwhere you perform end-to-end tests and then move it to balenaCloud when it's\nready for production.\n\nTo move a device between fleets on the same server, use the\n`balena device move` command instead of `balena join`.\n\nIf you don't specify a device hostname or IP, this command will automatically\nscan the local network for balenaOS devices and prompt you to select one\nfrom an interactive picker. This may require administrator/root privileges.\nLikewise, if the fleet option is not provided then a picker will be shown.\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 local flash path/to/balenaos.img",
-        "$ balena local flash path/to/balenaos.img --drive /dev/disk2",
-        "$ balena local flash path/to/balenaos.img --drive /dev/disk2 --yes"
+        "$ balena join",
+        "$ balena join balena.local",
+        "$ balena join balena.local --fleet MyFleet",
+        "$ balena join balena.local -f myorg/myfleet",
+        "$ balena join 192.168.1.25",
+        "$ balena join 192.168.1.25 --fleet MyFleet"
       ],
       "flags": {
-        "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",
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "name": "fleet",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "yes": {
-          "char": "y",
-          "description": "answer \"yes\" to all questions (non interactive use)",
-          "name": "yes",
-          "allowNo": false,
-          "type": "boolean"
+        "pollInterval": {
+          "char": "i",
+          "description": "the interval in minutes to check for updates",
+          "name": "pollInterval",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "local:flash",
+      "id": "join",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "offlineCompatible": true,
+      "authenticated": true,
+      "primary": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "local",
-        "flash.js"
+        "join",
+        "index.js"
       ]
     },
     "login": {
@@ -3209,6 +3094,121 @@
         "index.js"
       ]
     },
+    "local:configure": {
+      "aliases": [],
+      "args": {
+        "target": {
+          "description": "path of drive or image to configure",
+          "name": "target",
+          "required": true
+        }
+      },
+      "description": "(Re)configure a balenaOS drive or image.\n\nConfigure or reconfigure a balenaOS drive or image.",
+      "examples": [
+        "$ balena local configure /dev/sdc",
+        "$ balena local configure path/to/image.img"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "local:configure",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "root": true,
+      "offlineCompatible": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "local",
+        "configure.js"
+      ]
+    },
+    "local:flash": {
+      "aliases": [],
+      "args": {
+        "image": {
+          "description": "path to OS image",
+          "name": "image",
+          "required": true
+        }
+      },
+      "description": "Flash an image to a drive.\n\nFlash a balenaOS image to a drive.\nImage file may be one of: .img|.zip|.gz|.bz2|.xz\n\nIf --drive is not specified, then it will interactively\nshow a list of available drives for selection.",
+      "examples": [
+        "$ balena local flash path/to/balenaos.img",
+        "$ balena local flash path/to/balenaos.img --drive /dev/disk2",
+        "$ balena local flash path/to/balenaos.img --drive /dev/disk2 --yes"
+      ],
+      "flags": {
+        "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": "local:flash",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "offlineCompatible": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "local",
+        "flash.js"
+      ]
+    },
+    "leave": {
+      "aliases": [],
+      "args": {
+        "deviceIpOrHostname": {
+          "description": "the device IP or hostname",
+          "name": "deviceIpOrHostname"
+        }
+      },
+      "description": "Remove a local device from its balena fleet.\n\nRemove a local device from its balena fleet, causing the device to\n\"leave\" the server it is provisioned on. This effectively makes the device\n\"unmanaged\". The device must be running balenaOS.\n\nThe device entry on the server is preserved after running this command,\nso the device can subsequently re-join the server if needed.\n\nIf you don't specify a device hostname or IP, this command will automatically\nscan the local network for balenaOS devices and prompt you to select one\nfrom an interactive picker. This may require administrator/root privileges.",
+      "examples": [
+        "$ balena leave",
+        "$ balena leave balena.local",
+        "$ balena leave 192.168.1.25"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "leave",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "primary": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "leave",
+        "index.js"
+      ]
+    },
     "logout": {
       "aliases": [],
       "args": {},
@@ -4074,30 +4074,6 @@
         "validate.js"
       ]
     },
-    "settings": {
-      "aliases": [],
-      "args": {},
-      "description": "Print current settings.\n\nUse this command to display the current balena CLI settings.",
-      "examples": [
-        "$ balena settings"
-      ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "settings",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "settings",
-        "index.js"
-      ]
-    },
     "release-asset:delete": {
       "aliases": [],
       "args": {
@@ -4313,6 +4289,30 @@
         "upload.js"
       ]
     },
+    "settings": {
+      "aliases": [],
+      "args": {},
+      "description": "Print current settings.\n\nUse this command to display the current balena CLI settings.",
+      "examples": [
+        "$ balena settings"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "settings",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "settings",
+        "index.js"
+      ]
+    },
     "support": {
       "aliases": [],
       "args": {
@@ -4509,6 +4509,28 @@
         "rm.js"
       ]
     },
+    "util:available-drives": {
+      "aliases": [],
+      "args": {},
+      "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": "util:available-drives",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "offlineCompatible": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "util",
+        "available-drives.js"
+      ]
+    },
     "tag:list": {
       "aliases": [],
       "args": {},
@@ -4753,29 +4775,7 @@
         "whoami",
         "index.js"
       ]
-    },
-    "util:available-drives": {
-      "aliases": [],
-      "args": {},
-      "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": "util:available-drives",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "offlineCompatible": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "util",
-        "available-drives.js"
-      ]
     }
   },
-  "version": "23.2.12"
+  "version": "23.2.13"
 }