{
  "commands": {
    "api-key:generate": {
      "aliases": [],
      "args": {
        "name": {
          "description": "the API key name",
          "name": "name",
          "required": true
        },
        "expiryDate": {
          "description": "the expiry date of the API key as an ISO date string, or \"never\" for no expiry",
          "name": "expiryDate"
        }
      },
      "description": "Generate a new balenaCloud API key.\n\nGenerate a new balenaCloud API key for the current user, with the given\nname. The key will be logged to the console.\n\nThis key can be used to log into the CLI using 'balena login --token <key>',\nor to authenticate requests to the API with an 'Authorization: Bearer <key>' header.",
      "examples": [
        "$ balena api-key generate \"Jenkins Key\"",
        "$ balena api-key generate \"Jenkins Key\" 2025-10-30",
        "$ balena api-key generate \"Jenkins Key\" never"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "api-key:generate",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "api-key",
        "generate.js"
      ]
    },
    "api-key:list": {
      "aliases": [],
      "args": {},
      "description": "Print a list of balenaCloud API keys.\n\nPrint a list of balenaCloud API keys.\n\nPrint a list of balenaCloud API keys for the current user or for a specific fleet with the `--fleet` option.",
      "examples": [
        "$ balena api-key list"
      ],
      "flags": {
        "user": {
          "char": "u",
          "description": "show API keys for your user",
          "name": "user",
          "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": "api-key:list",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "api-key",
        "list.js"
      ]
    },
    "api-key:revoke": {
      "aliases": [],
      "args": {
        "ids": {
          "description": "the API key ids",
          "name": "ids",
          "required": true
        }
      },
      "description": "Revoke balenaCloud API keys.\n\nRevoke balenaCloud API keys with the given\ncomma-separated list of ids.\n\nThe given balenaCloud API keys will no longer be usable.",
      "examples": [
        "$ balena api-key revoke 123",
        "$ balena api-key revoke 123,124,456"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "api-key:revoke",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "api-key",
        "revoke.js"
      ]
    },
    "app:create": {
      "aliases": [],
      "args": {
        "name": {
          "description": "app name",
          "name": "name",
          "required": true
        }
      },
      "description": "Create an app.\n\nCreate a new balena app.\n\nYou can specify the organization the app 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 app'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 app create MyApp",
        "$ balena app create MyApp --organization mmyorg",
        "$ balena app create MyApp -o myorg --type raspberry-pi"
      ],
      "flags": {
        "organization": {
          "char": "o",
          "description": "handle of the organization the app should belong to",
          "name": "organization",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "type": {
          "char": "t",
          "description": "app device type (Check available types with `balena device-type list`)",
          "name": "type",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "app:create",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "app",
        "create.js"
      ]
    },
    "build": {
      "aliases": [],
      "args": {
        "source": {
          "description": "path of project source directory",
          "name": "source"
        }
      },
      "description": "Build a project locally.\n\nUse this command to build an image or a complete multicontainer project with\nthe provided docker daemon in your development machine or balena device.\n(See also the `balena push` command for the option of building images in the\nbalenaCloud build servers.)\n\nYou must specify either a fleet, or the device type and architecture.\n\nThis command will look into the given source directory (or the current working\ndirectory if one isn't specified) for a docker-compose.yml file, and if found,\neach service defined in the compose file will be built. If a compose file isn't\nfound, it will look for a Dockerfile[.template] file (or alternative Dockerfile\nspecified with the `--dockerfile` option), and if no dockerfile is found, it\nwill try to generate one.\n\nREGISTRY SECRETS  \nThe --registry-secrets option specifies a JSON or YAML file containing private\nDocker registry usernames and passwords to be used when pulling base images.\nSample registry-secrets YAML file:\n```\n\t'my-registry-server.com:25000':\n\t\tusername: ann\n\t\tpassword: hunter2\n\t'':  # Use the empty string to refer to the Docker Hub\n\t\tusername: mike\n\t\tpassword: cze14\n\t'eu.gcr.io':  # Google Container Registry\n\t\tusername: '_json_key'\n\t\tpassword: '{escaped contents of the GCR keyfile.json file}'\n```\nFor a sample project using registry secrets with the Google Container Registry,\ncheck: https://github.com/balena-io-examples/sample-gcr-registry-secrets\n\nIf the --registry-secrets option is not specified, and a secrets.yml or\nsecrets.json file exists in the balena directory (usually $HOME/.balena),\nthis file will be used instead.\n\nDOCKERIGNORE AND GITIGNORE FILES  \nBy default, the balena CLI will use a single \".dockerignore\" file (if any) at\nthe project root (--source directory) in order to decide which source files to\nexclude from the \"build context\" (tar stream) sent to balenaCloud, Docker\ndaemon or balenaEngine.  In a microservices (multicontainer) fleet, the\nsource directory is the directory that contains the \"docker-compose.yml\" file.\n\nThe --multi-dockerignore (-m) option may be used with microservices\n(multicontainer) fleets that define a docker-compose.yml file. When this\noption is used, each service subdirectory (defined by the `build` or\n`build.context` service properties in the docker-compose.yml file) is\nfiltered separately according to a .dockerignore file defined in the service\nsubdirectory. If no .dockerignore file exists in a service subdirectory, then\nonly the default .dockerignore patterns (see below) apply for that service\nsubdirectory.\n\nWhen the --multi-dockerignore (-m) option is used, the .dockerignore file (if\nany) defined at the overall project root will be used to filter files and\nsubdirectories other than service subdirectories. It will not have any effect\non service subdirectories, whether or not a service subdirectory defines its\nown .dockerignore file. Multiple .dockerignore files are not merged or added\ntogether, and cannot override or extend other files. This behavior maximizes\ncompatibility with the standard docker-compose tool, while still allowing a\nroot .dockerignore file (at the overall project root) to filter files and\nfolders that are outside service subdirectories.\n\nbalena CLI v11 also took .gitignore files into account. This behavior was\ndeprecated in CLI v12 and removed in CLI v13. Please use .dockerignore files\ninstead.\n\nDefault .dockerignore patterns  \nA few default/hardcoded dockerignore patterns are \"merged\" (in memory) with the\npatterns found in the applicable .dockerignore files, in the following order:\n```\n    **/.git\n    < user's patterns from the applicable '.dockerignore' file, if any >\n    !**/.balena\n    !**/.resin\n    !**/Dockerfile\n    !**/Dockerfile.*\n    !**/docker-compose.yml\n```\nThese patterns always apply, whether or not .dockerignore files exist in the\nproject. If necessary, the effect of the `**/.git` pattern may be modified by\nadding exception patterns to the applicable .dockerignore file(s), for example\n`!mysubmodule/.git`. For documentation on pattern format, see:\n- https://docs.docker.com/engine/reference/builder/#dockerignore-file\n- https://www.npmjs.com/package/@balena/dockerignore\n",
      "examples": [
        "$ balena build --fleet myFleet",
        "$ balena build ./source/ --fleet myorg/myfleet",
        "$ balena build --deviceType raspberrypi3 --emulated",
        "$ balena build --deviceType raspberrypi3 --arch armv7hf --emulated",
        "$ balena build --docker /var/run/docker.sock --fleet myFleet   # Linux, Mac",
        "$ balena build --docker //./pipe/docker_engine --fleet myFleet # Windows",
        "$ balena build --dockerHost my.docker.host --dockerPort 2376 --ca ca.pem --key key.pem --cert cert.pem -f myFleet"
      ],
      "flags": {
        "arch": {
          "char": "A",
          "description": "the architecture to build for",
          "name": "arch",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "deviceType": {
          "char": "d",
          "description": "the type of device this build is for",
          "name": "deviceType",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "fleet": {
          "char": "f",
          "description": "fleet name or slug (preferred)",
          "name": "fleet",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "emulated": {
          "char": "e",
          "description": "Use QEMU for ARM architecture emulation during the image build",
          "name": "emulated",
          "allowNo": false,
          "type": "boolean"
        },
        "dockerfile": {
          "description": "Alternative Dockerfile name/path, relative to the source folder",
          "name": "dockerfile",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "nologs": {
          "description": "Hide the image build log output (produce less verbose output)",
          "name": "nologs",
          "allowNo": false,
          "type": "boolean"
        },
        "multi-dockerignore": {
          "char": "m",
          "description": "Have each service use its own .dockerignore file. See \"balena help build\".",
          "name": "multi-dockerignore",
          "allowNo": false,
          "type": "boolean"
        },
        "noparent-check": {
          "description": "Disable project validation check of 'docker-compose.yml' file in parent folder",
          "name": "noparent-check",
          "allowNo": false,
          "type": "boolean"
        },
        "registry-secrets": {
          "char": "R",
          "description": "Path to a YAML or JSON file with passwords for a private Docker registry",
          "name": "registry-secrets",
          "hasDynamicHelp": false,
          "multiple": false,
          "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"
        },
        "projectName": {
          "char": "n",
          "description": "Name prefix for locally built images. This is the 'projectName' portion\nin 'projectName_serviceName:tag'. The default is the directory name.",
          "name": "projectName",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "tag": {
          "char": "t",
          "description": "Tag locally built Docker images. This is the 'tag' portion\nin 'projectName_serviceName:tag'. The default is 'latest'.",
          "name": "tag",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "buildArg": {
          "char": "B",
          "description": "[Deprecated] Set a build-time variable (eg. \"-B 'ARG=value'\"). Can be specified multiple times.",
          "name": "buildArg",
          "hasDynamicHelp": false,
          "multiple": true,
          "type": "option"
        },
        "cache-from": {
          "description": "Comma-separated list (no spaces) of image names for build cache resolution. Implements the same feature as the \"docker build --cache-from\" option.",
          "name": "cache-from",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "nocache": {
          "description": "Don't use docker layer caching when building",
          "name": "nocache",
          "allowNo": false,
          "type": "boolean"
        },
        "pull": {
          "description": "Pull the base images again even if they exist locally",
          "name": "pull",
          "allowNo": false,
          "type": "boolean"
        },
        "squash": {
          "description": "Squash newly built layers into a single new layer",
          "name": "squash",
          "allowNo": false,
          "type": "boolean"
        },
        "docker": {
          "char": "P",
          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
          "name": "docker",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "dockerHost": {
          "char": "h",
          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
          "name": "dockerHost",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "dockerPort": {
          "char": "p",
          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
          "name": "dockerPort",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "ca": {
          "description": "Docker host TLS certificate authority file",
          "name": "ca",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "cert": {
          "description": "Docker host TLS certificate file",
          "name": "cert",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "key": {
          "description": "Docker host TLS key file",
          "name": "key",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "build",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "primary": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "build",
        "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": {},
      "description": "Generate a config.json file.\n\nGenerate a config.json file for a device or fleet.\n\nThe target balenaOS version must be specified with the --version option.\n\nThe '--dev' option is used to configure balenaOS to operate in development mode,\nallowing unauthenticated root ssh access and exposing network ports such as\nbalenaEngine's 2375 (unencrypted). This option causes `\"developmentMode\": true`\nto be inserted in the 'config.json' file in the image's boot partition. Development\nmode (as a configurable option) is applicable to balenaOS releases from early\n2022. Older releases have separate development and production balenaOS images\nthat cannot be reconfigured through 'config.json' or the '--dev' option. Do not\nconfuse the balenaOS \"development mode\" with a device's \"local mode\", the latter\nbeing a supervisor feature that allows the \"balena push\" command to push a user's\napplication directly to a device in the local network.\n\nThe '--secureBoot' option is used to configure a balenaOS installer image to opt-in\nsecure boot and disk encryption.\n\nTo configure an image for a fleet of mixed device types, use the --fleet option\nalongside the --deviceType option to specify the target device type.\n\nTo avoid interactive questions, specify a command line option for each question that\nwould otherwise be asked.\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 config generate --device 7cf02a6 --version 2.12.7",
        "$ balena config generate --device 7cf02a6 --version 2.12.7 --deviceApiKey <existingDeviceKey>",
        "$ balena config generate --device 7cf02a6 --version 2.12.7 --output config.json",
        "$ balena config generate --fleet myorg/fleet --version 2.12.7 --dev",
        "$ balena config generate --fleet myorg/fleet --version 2.12.7 --secureBoot",
        "$ balena config generate --fleet myorg/fleet --version 2.12.7 --deviceType fincm3",
        "$ balena config generate --fleet myorg/fleet --version 2.12.7 --output config.json",
        "$ balena config generate --fleet myorg/fleet --version 2.12.7 --network wifi --wifiSsid mySsid --wifiKey abcdefgh --appUpdatePollInterval 15"
      ],
      "flags": {
        "version": {
          "description": "a balenaOS version",
          "name": "version",
          "required": true,
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "fleet": {
          "char": "f",
          "description": "fleet name or slug (preferred)",
          "exclusive": [
            "device"
          ],
          "name": "fleet",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "dev": {
          "description": "Configure balenaOS to operate in development mode",
          "name": "dev",
          "allowNo": false,
          "type": "boolean"
        },
        "secureBoot": {
          "description": "Configure balenaOS installer to opt-in secure boot and disk encryption",
          "name": "secureBoot",
          "allowNo": false,
          "type": "boolean"
        },
        "device": {
          "char": "d",
          "description": "device UUID",
          "exclusive": [
            "fleet",
            "provisioning-key-name",
            "provisioning-key-expiry-date"
          ],
          "name": "device",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "deviceApiKey": {
          "char": "k",
          "description": "custom device key - note that this is only supported on balenaOS 2.0.3+",
          "name": "deviceApiKey",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "deviceType": {
          "description": "device type slug (run 'balena device-type list' for possible values)",
          "name": "deviceType",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "output": {
          "char": "o",
          "description": "path of output file",
          "name": "output",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "network": {
          "description": "the network type to use: ethernet or wifi",
          "name": "network",
          "hasDynamicHelp": false,
          "multiple": false,
          "options": [
            "ethernet",
            "wifi"
          ],
          "type": "option"
        },
        "wifiSsid": {
          "description": "the wifi ssid to use (used only if --network is set to wifi)",
          "name": "wifiSsid",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "wifiKey": {
          "description": "the wifi key to use (used only if --network is set to wifi)",
          "name": "wifiKey",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "appUpdatePollInterval": {
          "description": "supervisor cloud polling interval in minutes (e.g. for device variables)",
          "name": "appUpdatePollInterval",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "initial-device-name": {
          "description": "This option will set the device name when the device provisions",
          "name": "initial-device-name",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "provisioning-key-name": {
          "description": "custom key name assigned to generated provisioning api key",
          "exclusive": [
            "device"
          ],
          "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)",
          "exclusive": [
            "device"
          ],
          "name": "provisioning-key-expiry-date",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "config:generate",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "config",
        "generate.js"
      ]
    },
    "config:inject": {
      "aliases": [],
      "args": {
        "file": {
          "description": "the path to the config.json file to inject",
          "name": "file",
          "required": true
        }
      },
      "description": "Inject a config.json file to a balenaOS image or attached media.\n\nInject a 'config.json' file to a balenaOS image file or attached SD card or\nUSB stick.\n\nDocumentation for the balenaOS 'config.json' file can be found at:\nhttps://www.balena.io/docs/reference/OS/configuration/",
      "examples": [
        "$ balena config inject my/config.json",
        "$ balena config inject my/config.json --drive /dev/disk2"
      ],
      "flags": {
        "drive": {
          "char": "d",
          "description": "path to OS image file (e.g. balena.img) or block device (e.g. /dev/disk2)",
          "name": "drive",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "config:inject",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "root": true,
      "offlineCompatible": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "config",
        "inject.js"
      ]
    },
    "config:read": {
      "aliases": [],
      "args": {},
      "description": "Read the config.json file of a balenaOS image or attached media.\n\nRead the 'config.json' file of a balenaOS image file or attached SD card or\nUSB stick.\n\nDocumentation for the balenaOS 'config.json' file can be found at:\nhttps://www.balena.io/docs/reference/OS/configuration/",
      "examples": [
        "$ balena config read",
        "$ balena config read --drive /dev/disk2",
        "$ balena config read --drive balena.img"
      ],
      "flags": {
        "json": {
          "description": "Format output as json.",
          "helpGroup": "GLOBAL",
          "name": "json",
          "allowNo": false,
          "type": "boolean"
        },
        "drive": {
          "char": "d",
          "description": "path to OS image file (e.g. balena.img) or block device (e.g. /dev/disk2)",
          "name": "drive",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "config:read",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": true,
      "root": true,
      "offlineCompatible": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "config",
        "read.js"
      ]
    },
    "config:reconfigure": {
      "aliases": [],
      "args": {},
      "description": "Interactively reconfigure a balenaOS image file or attached media.\n\nInteractively reconfigure a balenaOS image file or attached media.\n\nThis command extracts the device UUID from the 'config.json' file of the\nchosen balenaOS image file or attached media, and then passes the UUID as\nthe '--device' argument to the 'balena os configure' command.\n\nFor finer-grained or scripted control of the operation, use the\n'balena config read' and 'balena os configure' commands separately.",
      "examples": [
        "$ balena config reconfigure",
        "$ balena config reconfigure --drive /dev/disk3",
        "$ balena config reconfigure --drive balena.img --advanced"
      ],
      "flags": {
        "drive": {
          "char": "d",
          "description": "path to OS image file (e.g. balena.img) or block device (e.g. /dev/disk2)",
          "name": "drive",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "advanced": {
          "char": "v",
          "description": "show advanced commands",
          "name": "advanced",
          "allowNo": false,
          "type": "boolean"
        },
        "version": {
          "description": "balenaOS version, for example \"2.32.0\" or \"2.44.0+rev1\"",
          "name": "version",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "config:reconfigure",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "root": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "config",
        "reconfigure.js"
      ]
    },
    "config:write": {
      "aliases": [],
      "args": {
        "key": {
          "description": "the key of the config parameter to write",
          "name": "key",
          "required": true
        },
        "value": {
          "description": "the value of the config parameter to write",
          "name": "value",
          "required": true
        }
      },
      "description": "Write a key-value pair to the config.json file of an OS image or attached media.\n\nWrite a key-value pair to the 'config.json' file of a balenaOS image file or\nattached SD card or USB stick.\n\nDocumentation for the balenaOS 'config.json' file can be found at:\nhttps://www.balena.io/docs/reference/OS/configuration/",
      "examples": [
        "$ balena config write ntpServers \"0.resinio.pool.ntp.org 1.resinio.pool.ntp.org\"",
        "$ balena config write --drive /dev/disk2 hostname custom-hostname",
        "$ balena config write --drive balena.img os.network.connectivity.interval 300"
      ],
      "flags": {
        "drive": {
          "char": "d",
          "description": "path to OS image file (e.g. balena.img) or block device (e.g. /dev/disk2)",
          "name": "drive",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "config:write",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "root": true,
      "offlineCompatible": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "config",
        "write.js"
      ]
    },
    "deploy": {
      "aliases": [],
      "args": {
        "fleet": {
          "description": "fleet name or slug (preferred)",
          "name": "fleet",
          "required": true
        },
        "image": {
          "description": "the image to deploy",
          "name": "image"
        }
      },
      "description": "Deploy a single image or a multicontainer project to a balena fleet.\n\nUsage: `deploy <fleet> ([image] | --build [--source build-dir])`\n\nUse this command to deploy an image or a complete multicontainer project to a\nfleet, optionally building it first. The source images are searched for\n(and optionally built) using the docker daemon in your development machine or\nbalena device. (See also the `balena push` command for the option of building\nthe image in the balenaCloud build servers.)\n\nUnless an image is specified, this command will look into the current directory\n(or the one specified by --source) for a docker-compose.yml file.  If one is\nfound, this command will deploy each service defined in the compose file,\nbuilding it first if an image for it doesn't exist. Image names will be looked\nup according to the scheme: `<projectName>_<serviceName>`.\n\nIf a compose file isn't found, the command will look for a Dockerfile[.template]\nfile (or alternative Dockerfile specified with the `-f` option), and if yet\nthat isn't found, it will try to generate one.\n\nTo deploy to a fleet where you are a collaborator, use fleet slug including the\norganization:  `balena deploy <organization>/<fleet>`.\n\nREGISTRY SECRETS  \nThe --registry-secrets option specifies a JSON or YAML file containing private\nDocker registry usernames and passwords to be used when pulling base images.\nSample registry-secrets YAML file:\n```\n\t'my-registry-server.com:25000':\n\t\tusername: ann\n\t\tpassword: hunter2\n\t'':  # Use the empty string to refer to the Docker Hub\n\t\tusername: mike\n\t\tpassword: cze14\n\t'eu.gcr.io':  # Google Container Registry\n\t\tusername: '_json_key'\n\t\tpassword: '{escaped contents of the GCR keyfile.json file}'\n```\nFor a sample project using registry secrets with the Google Container Registry,\ncheck: https://github.com/balena-io-examples/sample-gcr-registry-secrets\n\nIf the --registry-secrets option is not specified, and a secrets.yml or\nsecrets.json file exists in the balena directory (usually $HOME/.balena),\nthis file will be used instead.\n\nDOCKERIGNORE AND GITIGNORE FILES  \nBy default, the balena CLI will use a single \".dockerignore\" file (if any) at\nthe project root (--source directory) in order to decide which source files to\nexclude from the \"build context\" (tar stream) sent to balenaCloud, Docker\ndaemon or balenaEngine.  In a microservices (multicontainer) fleet, the\nsource directory is the directory that contains the \"docker-compose.yml\" file.\n\nThe --multi-dockerignore (-m) option may be used with microservices\n(multicontainer) fleets that define a docker-compose.yml file. When this\noption is used, each service subdirectory (defined by the `build` or\n`build.context` service properties in the docker-compose.yml file) is\nfiltered separately according to a .dockerignore file defined in the service\nsubdirectory. If no .dockerignore file exists in a service subdirectory, then\nonly the default .dockerignore patterns (see below) apply for that service\nsubdirectory.\n\nWhen the --multi-dockerignore (-m) option is used, the .dockerignore file (if\nany) defined at the overall project root will be used to filter files and\nsubdirectories other than service subdirectories. It will not have any effect\non service subdirectories, whether or not a service subdirectory defines its\nown .dockerignore file. Multiple .dockerignore files are not merged or added\ntogether, and cannot override or extend other files. This behavior maximizes\ncompatibility with the standard docker-compose tool, while still allowing a\nroot .dockerignore file (at the overall project root) to filter files and\nfolders that are outside service subdirectories.\n\nbalena CLI v11 also took .gitignore files into account. This behavior was\ndeprecated in CLI v12 and removed in CLI v13. Please use .dockerignore files\ninstead.\n\nDefault .dockerignore patterns  \nA few default/hardcoded dockerignore patterns are \"merged\" (in memory) with the\npatterns found in the applicable .dockerignore files, in the following order:\n```\n    **/.git\n    < user's patterns from the applicable '.dockerignore' file, if any >\n    !**/.balena\n    !**/.resin\n    !**/Dockerfile\n    !**/Dockerfile.*\n    !**/docker-compose.yml\n```\nThese patterns always apply, whether or not .dockerignore files exist in the\nproject. If necessary, the effect of the `**/.git` pattern may be modified by\nadding exception patterns to the applicable .dockerignore file(s), for example\n`!mysubmodule/.git`. For documentation on pattern format, see:\n- https://docs.docker.com/engine/reference/builder/#dockerignore-file\n- https://www.npmjs.com/package/@balena/dockerignore\n",
      "examples": [
        "$ balena deploy myFleet",
        "$ balena deploy myorg/myfleet --build --source myBuildDir/",
        "$ balena deploy myorg/myfleet --build --source myBuildDir/ --note \"this is the note for this release\"",
        "$ balena deploy myorg/myfleet myRepo/myImage",
        "$ balena deploy myFleet myRepo/myImage --release-tag key1 \"\" key2 \"value2 with spaces\""
      ],
      "flags": {
        "source": {
          "char": "s",
          "description": "specify an alternate source directory; default is the working directory",
          "name": "source",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "build": {
          "char": "b",
          "description": "force a rebuild before deploy",
          "name": "build",
          "allowNo": false,
          "type": "boolean"
        },
        "nologupload": {
          "description": "don't upload build logs to the dashboard with image (if building)",
          "name": "nologupload",
          "allowNo": false,
          "type": "boolean"
        },
        "release-tag": {
          "description": "Set release tags if the image deployment is successful. Multiple\narguments may be provided, alternating tag keys and values (see examples).\nHint: Empty values may be specified with \"\" (bash, cmd.exe) or '\"\"' (PowerShell).",
          "name": "release-tag",
          "hasDynamicHelp": false,
          "multiple": true,
          "type": "option"
        },
        "draft": {
          "description": "Deploy 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"
        },
        "emulated": {
          "char": "e",
          "description": "Use QEMU for ARM architecture emulation during the image build",
          "name": "emulated",
          "allowNo": false,
          "type": "boolean"
        },
        "dockerfile": {
          "description": "Alternative Dockerfile name/path, relative to the source folder",
          "name": "dockerfile",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "nologs": {
          "description": "Hide the image build log output (produce less verbose output)",
          "name": "nologs",
          "allowNo": false,
          "type": "boolean"
        },
        "multi-dockerignore": {
          "char": "m",
          "description": "Have each service use its own .dockerignore file. See \"balena help build\".",
          "name": "multi-dockerignore",
          "allowNo": false,
          "type": "boolean"
        },
        "noparent-check": {
          "description": "Disable project validation check of 'docker-compose.yml' file in parent folder",
          "name": "noparent-check",
          "allowNo": false,
          "type": "boolean"
        },
        "registry-secrets": {
          "char": "R",
          "description": "Path to a YAML or JSON file with passwords for a private Docker registry",
          "name": "registry-secrets",
          "hasDynamicHelp": false,
          "multiple": false,
          "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"
        },
        "projectName": {
          "char": "n",
          "description": "Name prefix for locally built images. This is the 'projectName' portion\nin 'projectName_serviceName:tag'. The default is the directory name.",
          "name": "projectName",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "tag": {
          "char": "t",
          "description": "Tag locally built Docker images. This is the 'tag' portion\nin 'projectName_serviceName:tag'. The default is 'latest'.",
          "name": "tag",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "buildArg": {
          "char": "B",
          "description": "[Deprecated] Set a build-time variable (eg. \"-B 'ARG=value'\"). Can be specified multiple times.",
          "name": "buildArg",
          "hasDynamicHelp": false,
          "multiple": true,
          "type": "option"
        },
        "cache-from": {
          "description": "Comma-separated list (no spaces) of image names for build cache resolution. Implements the same feature as the \"docker build --cache-from\" option.",
          "name": "cache-from",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "nocache": {
          "description": "Don't use docker layer caching when building",
          "name": "nocache",
          "allowNo": false,
          "type": "boolean"
        },
        "pull": {
          "description": "Pull the base images again even if they exist locally",
          "name": "pull",
          "allowNo": false,
          "type": "boolean"
        },
        "squash": {
          "description": "Squash newly built layers into a single new layer",
          "name": "squash",
          "allowNo": false,
          "type": "boolean"
        },
        "docker": {
          "char": "P",
          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
          "name": "docker",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "dockerHost": {
          "char": "h",
          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
          "name": "dockerHost",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "dockerPort": {
          "char": "p",
          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
          "name": "dockerPort",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "ca": {
          "description": "Docker host TLS certificate authority file",
          "name": "ca",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "cert": {
          "description": "Docker host TLS certificate file",
          "name": "cert",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "key": {
          "description": "Docker host TLS key file",
          "name": "key",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "deploy",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "primary": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "deploy",
        "index.js"
      ]
    },
    "device-type:list": {
      "aliases": [],
      "args": {},
      "description": "List the device types supported by balena (like 'raspberrypi3' or 'intel-nuc').\n\nList the device types supported by balena (like 'raspberrypi3' or 'intel-nuc').\n\nBy default, only actively supported device types are listed.\nThe --all option can be used to list all device types, including those that are\nno longer supported by balena.",
      "examples": [
        "$ balena device-type list",
        "$ balena device-type list --all"
      ],
      "flags": {
        "json": {
          "description": "Format output as json.",
          "helpGroup": "GLOBAL",
          "name": "json",
          "allowNo": false,
          "type": "boolean"
        },
        "all": {
          "description": "include device types no longer supported by balena",
          "name": "all",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device-type:list",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device-type",
        "list.js"
      ]
    },
    "device:deactivate": {
      "aliases": [],
      "args": {
        "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"
      ],
      "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' (exludes invalidated & pre-releases),\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",
        "list.js"
      ]
    },
    "device:local-mode": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "the uuid of the device to manage",
          "name": "uuid",
          "required": true
        }
      },
      "description": "Get or manage the local mode status for a device.\n\nOutput current local mode status, or enable/disable local mode\nfor specified device.",
      "examples": [
        "$ balena device local-mode 23c73a1",
        "$ balena device local-mode 23c73a1 --enable",
        "$ balena device local-mode 23c73a1 --disable",
        "$ balena device local-mode 23c73a1 --status"
      ],
      "flags": {
        "enable": {
          "description": "enable local mode",
          "exclusive": [
            "disable",
            "status"
          ],
          "name": "enable",
          "allowNo": false,
          "type": "boolean"
        },
        "disable": {
          "description": "disable local mode",
          "exclusive": [
            "enable",
            "status"
          ],
          "name": "disable",
          "allowNo": false,
          "type": "boolean"
        },
        "status": {
          "description": "output boolean indicating local mode status",
          "exclusive": [
            "enable",
            "disable"
          ],
          "name": "status",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:local-mode",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "local-mode.js"
      ]
    },
    "device:logs": {
      "aliases": [],
      "args": {
        "device": {
          "description": "device UUID, IP, or .local address",
          "name": "device",
          "required": true
        }
      },
      "description": "Show device logs.\n\nShow logs for a specific device.\n\nBy default, the command prints all log messages and exits.\n\nTo continuously stream output, and see new logs in real time, use the `--tail` option.\n\nIf an IP or .local address is passed to this command, logs are displayed from\na local mode device with that address. Note that --tail is implied\nwhen this command is provided a local mode device.\n\nLogs from a single service can be displayed with the --service flag. Just system logs\ncan be shown with the --system flag. Note that these flags can be used together.\n\nNote: --service and --system flags must come after the device parameter, as per examples.",
      "examples": [
        "$ balena device logs 23c73a1",
        "$ balena device logs 23c73a1 --tail",
        "",
        "$ balena device logs 192.168.0.31",
        "$ balena device logs 192.168.0.31 --service my-service",
        "$ balena device logs 192.168.0.31 --service my-service-1 --service my-service-2",
        "",
        "$ balena device logs 23c73a1.local --system",
        "$ balena device logs 23c73a1.local --system --service my-service"
      ],
      "flags": {
        "max-retry": {
          "description": "Maximum number of reconnection attempts on \"connection lost\" errors\n(use 0 to disable auto reconnection).",
          "name": "max-retry",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "tail": {
          "char": "t",
          "description": "continuously stream output",
          "name": "tail",
          "allowNo": false,
          "type": "boolean"
        },
        "service": {
          "char": "s",
          "description": "Reject logs not originating from this service.\nThis can be used in combination with --system or other --service flags.",
          "name": "service",
          "hasDynamicHelp": false,
          "multiple": true,
          "type": "option"
        },
        "system": {
          "char": "S",
          "description": "Only show system logs. This can be used in combination with --service.",
          "name": "system",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:logs",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "primary": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "logs.js"
      ]
    },
    "device:move": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "comma-separated list (no blank spaces) of device UUIDs to be moved",
          "name": "uuid",
          "required": true
        }
      },
      "description": "Move one or more devices to another fleet.\n\nMove one or more devices to another fleet.\n\nIf --fleet is omitted, the fleet will be prompted for interactively.\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 move 7cf02a6",
        "$ balena device move 7cf02a6,dc39e52",
        "$ balena device move 7cf02a6 --fleet MyNewFleet",
        "$ balena device move 7cf02a6 -f myorg/mynewfleet"
      ],
      "flags": {
        "fleet": {
          "char": "f",
          "description": "fleet name or slug (preferred)",
          "name": "fleet",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:move",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "move.js"
      ]
    },
    "device:note": {
      "aliases": [],
      "args": {
        "note": {
          "description": "note content",
          "name": "note"
        }
      },
      "description": "Set a device note.\n\nSet or update a device note. If the note argument is not provided,\nit will be read from stdin.\n\nTo view device notes, use the `balena device <uuid>` command.",
      "examples": [
        "$ balena device note \"My useful note\" --device 7cf02a6",
        "$ cat note.txt | balena device note --device 7cf02a6"
      ],
      "flags": {
        "device": {
          "char": "d",
          "description": "device UUID",
          "name": "device",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:note",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "note.js"
      ]
    },
    "device:os-update": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "the uuid of the device to update",
          "name": "uuid",
          "required": true
        }
      },
      "description": "Start a Host OS update for a device.\n\nStart a Host OS update for a device.\n\nNote this command will ask for confirmation interactively.\nThis can be avoided by passing the `--yes` option.\n\nRequires balenaCloud; will not work with openBalena or standalone balenaOS.",
      "examples": [
        "$ balena device os-update 23c73a1",
        "$ balena device os-update 23c73a1 --version 2.101.7",
        "$ balena device os-update 23c73a1 --version 2.31.0+rev1.prod",
        "$ balena device os-update 23c73a1 --include-draft"
      ],
      "flags": {
        "version": {
          "description": "a balenaOS version",
          "exclusive": [
            "include-draft"
          ],
          "name": "version",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "include-draft": {
          "description": "include pre-release balenaOS versions",
          "exclusive": [
            "version"
          ],
          "name": "include-draft",
          "allowNo": false,
          "type": "boolean"
        },
        "yes": {
          "char": "y",
          "description": "answer \"yes\" to all questions (non interactive use)",
          "name": "yes",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:os-update",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "os-update.js"
      ]
    },
    "device:pin": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "the uuid of the device to pin to a release",
          "name": "uuid",
          "required": true
        },
        "releaseToPinTo": {
          "description": "the commit of the release for the device to get pinned to",
          "name": "releaseToPinTo"
        }
      },
      "description": "Pin a device to a release.\n\nPin a device to a release.\n\nNote, if the commit is omitted, the currently pinned release will be printed, with instructions for how to see a list of releases",
      "examples": [
        "$ balena device pin 7cf02a6",
        "$ balena device pin 7cf02a6 91165e5"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:pin",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "pin.js"
      ]
    },
    "device:public-url": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "the uuid of the device to manage",
          "name": "uuid",
          "required": true
        }
      },
      "description": "Get or manage the public URL for a device.\n\nThis command will output the current public URL for the\nspecified device.  It can also enable or disable the URL,\nor output the enabled status, using the respective options.",
      "examples": [
        "$ balena device public-url 23c73a1",
        "$ balena device public-url 23c73a1 --enable",
        "$ balena device public-url 23c73a1 --disable",
        "$ balena device public-url 23c73a1 --status"
      ],
      "flags": {
        "enable": {
          "description": "enable the public URL",
          "exclusive": [
            "disable",
            "status"
          ],
          "name": "enable",
          "allowNo": false,
          "type": "boolean"
        },
        "disable": {
          "description": "disable the public URL",
          "exclusive": [
            "enable",
            "status"
          ],
          "name": "disable",
          "allowNo": false,
          "type": "boolean"
        },
        "status": {
          "description": "determine if public URL is enabled",
          "exclusive": [
            "enable",
            "disable"
          ],
          "name": "status",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:public-url",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "public-url.js"
      ]
    },
    "device:purge": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "comma-separated list (no blank spaces) of device UUIDs",
          "name": "uuid",
          "required": true
        }
      },
      "description": "Purge data from a device.\n\nPurge data from a device.\nThis will clear the device's \"/data\" directory.\n\nMultiple devices may be specified with a comma-separated list\nof values (no spaces).",
      "examples": [
        "$ balena device purge 23c73a1",
        "$ balena device purge 55d43b3,23c73a1"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:purge",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "purge.js"
      ]
    },
    "device:reboot": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "the uuid of the device to reboot",
          "name": "uuid",
          "required": true
        }
      },
      "description": "Restart a device.\n\nRemotely reboot a device.",
      "examples": [
        "$ balena device reboot 23c73a1"
      ],
      "flags": {
        "force": {
          "char": "f",
          "description": "force action if the update lock is set",
          "name": "force",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:reboot",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "reboot.js"
      ]
    },
    "device:register": {
      "aliases": [],
      "args": {
        "fleet": {
          "description": "fleet name or slug (preferred)",
          "name": "fleet",
          "required": true
        }
      },
      "description": "Register a new device.\n\nRegister a new device with a balena fleet.\n\nIf --uuid is not provided, a new UUID will be automatically assigned.\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 register MyFleet",
        "$ balena device register MyFleet --uuid <uuid>",
        "$ balena device register myorg/myfleet --uuid <uuid>",
        "$ balena device register myorg/myfleet --uuid <uuid> --deviceType <deviceTypeSlug>"
      ],
      "flags": {
        "uuid": {
          "char": "u",
          "description": "custom uuid",
          "name": "uuid",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "deviceType": {
          "description": "device type slug (run 'balena device-type list' for possible values)",
          "name": "deviceType",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:register",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "register.js"
      ]
    },
    "device:rename": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "the uuid of the device to rename",
          "name": "uuid",
          "required": true
        },
        "newName": {
          "description": "the new name for the device",
          "name": "newName"
        }
      },
      "description": "Rename a device.\n\nRename a device.\n\nNote, if the name is omitted, it will be prompted for interactively.",
      "examples": [
        "$ balena device rename 7cf02a6",
        "$ balena device rename 7cf02a6 MyPi"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:rename",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "rename.js"
      ]
    },
    "device:restart": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "comma-separated list (no blank spaces) of device UUIDs to restart",
          "name": "uuid",
          "required": true
        }
      },
      "description": "Restart containers on a device.\n\nRestart containers on a device.\nIf the --service flag is provided, then only those services' containers\nwill be restarted, otherwise all containers on the device will be restarted.\n\nMultiple devices and services may be specified with a comma-separated list\nof values (no spaces).\n\nNote this does not reboot the device, to do so use instead `balena device reboot`.",
      "examples": [
        "$ balena device restart 23c73a1",
        "$ balena device restart 55d43b3,23c73a1",
        "$ balena device restart 23c73a1 --service myService",
        "$ balena device restart 23c73a1 -s myService1,myService2"
      ],
      "flags": {
        "service": {
          "char": "s",
          "description": "comma-separated list (no blank spaces) of service names to restart",
          "name": "service",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:restart",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "restart.js"
      ]
    },
    "device:rm": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "comma-separated list (no blank spaces) of device UUIDs to be removed",
          "name": "uuid",
          "required": true
        }
      },
      "description": "Remove one or more devices.\n\nRemove one or more devices from balena.\n\nNote this command asks for confirmation interactively.\nYou can avoid this by passing the `--yes` option.",
      "examples": [
        "$ balena device rm 7cf02a6",
        "$ balena device rm 7cf02a6,dc39e52",
        "$ balena device rm 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:rm",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "rm.js"
      ]
    },
    "device:shutdown": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "the uuid of the device to shutdown",
          "name": "uuid",
          "required": true
        }
      },
      "description": "Shutdown a device.\n\nRemotely shutdown a device.",
      "examples": [
        "$ balena device shutdown 23c73a1"
      ],
      "flags": {
        "force": {
          "char": "f",
          "description": "force action if the update lock is set",
          "name": "force",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:shutdown",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "shutdown.js"
      ]
    },
    "device:ssh": {
      "aliases": [],
      "args": {
        "fleetOrDevice": {
          "description": "fleet name/slug, device uuid, or address of local device",
          "name": "fleetOrDevice",
          "required": true
        },
        "service": {
          "description": "service name, if connecting to a container",
          "name": "service",
          "required": false
        }
      },
      "description": "Open a SSH prompt on a device's host OS or service container.\n\nStart a shell on a local or remote device. If a service name is not provided,\na shell will be opened on the host OS.\n\nIf a fleet is provided, an interactive menu will be presented for the selection\nof an online device. A shell will then be opened for the host OS or service\ncontainer of the chosen device.\n\nFor local devices, the IP address and .local domain name are supported.\nIf the device is referenced by IP or `.local` address, the connection\nis initiated directly to balenaOS on port `22222` via an\nopenssh-compatible client. Otherwise, any connection initiated remotely\ntraverses the balenaCloud VPN.\n\nCommands may be piped to the standard input for remote execution (see examples).\nNote however that remote command execution on service containers (as opposed to\nthe host OS) is not currently possible when a device UUID is used (instead of\nan IP address) because of a balenaCloud backend limitation.\n\nNote: `balena ssh` requires an openssh-compatible client to be correctly\ninstalled in your shell environment. For more information (including Windows\nsupport) please check:\n\thttps://github.com/balena-io/balena-cli/blob/master/INSTALL.md#additional-dependencies,",
      "examples": [
        "$ balena device ssh MyFleet",
        "$ balena device ssh f49cefd",
        "$ balena device ssh f49cefd my-service",
        "$ balena device ssh f49cefd --port <port>",
        "$ balena device ssh 192.168.0.1 --verbose",
        "$ balena device ssh f49cefd.local my-service",
        "$ echo \"uptime; exit;\" | balena device ssh f49cefd",
        "$ echo \"uptime; exit;\" | balena device ssh 192.168.0.1 myService"
      ],
      "flags": {
        "port": {
          "char": "p",
          "description": "SSH server port number (default 22222) if the target is an IP address or .local\nhostname. Otherwise, port number for the balenaCloud gateway (default 22).",
          "name": "port",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "tty": {
          "char": "t",
          "description": "force pseudo-terminal allocation (bypass TTY autodetection for stdin)",
          "name": "tty",
          "allowNo": false,
          "type": "boolean"
        },
        "verbose": {
          "char": "v",
          "description": "increase verbosity",
          "name": "verbose",
          "allowNo": false,
          "type": "boolean"
        },
        "noproxy": {
          "description": "bypass global proxy configuration for the ssh connection",
          "name": "noproxy",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:ssh",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "primary": true,
      "offlineCompatible": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "ssh.js"
      ]
    },
    "device:start-service": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "comma-separated list (no blank spaces) of device UUIDs",
          "name": "uuid",
          "required": true
        },
        "service": {
          "description": "comma-separated list (no blank spaces) of service names",
          "name": "service",
          "required": true
        }
      },
      "description": "Start containers on a device.\n\nStart containers on a device.\n\nMultiple devices and services may be specified with a comma-separated list\nof values (no spaces).",
      "examples": [
        "$ balena device start-service 23c73a1 myService",
        "$ balena device start-service 23c73a1 myService1,myService2"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:start-service",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "start-service.js"
      ]
    },
    "device:stop-service": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "comma-separated list (no blank spaces) of device UUIDs",
          "name": "uuid",
          "required": true
        },
        "service": {
          "description": "comma-separated list (no blank spaces) of service names",
          "name": "service",
          "required": true
        }
      },
      "description": "Stop containers on a device.\n\nStop containers on a device.\n\nMultiple devices and services may be specified with a comma-separated list\nof values (no spaces).",
      "examples": [
        "$ balena device stop-service 23c73a1 myService",
        "$ balena device stop-service 23c73a1 myService1,myService2"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "device:stop-service",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "device",
        "stop-service.js"
      ]
    },
    "device:track-fleet": {
      "aliases": [],
      "args": {
        "uuid": {
          "description": "the uuid of the device to make track the fleet's release",
          "name": "uuid",
          "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": {},
      "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": "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"
      ]
    },
    "fleet:create": {
      "aliases": [],
      "args": {
        "name": {
          "description": "fleet name",
          "name": "name",
          "required": true
        }
      },
      "description": "Create a fleet.\n\nCreate a new balena fleet.\n\nYou can specify the organization the fleet 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 fleet'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 fleet create MyFleet",
        "$ balena fleet create MyFleet --organization mmyorg",
        "$ balena fleet create MyFleet -o myorg --type raspberry-pi"
      ],
      "flags": {
        "organization": {
          "char": "o",
          "description": "handle of the organization the fleet should belong to",
          "name": "organization",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "type": {
          "char": "t",
          "description": "fleet device type (Check available types with `balena device-type list`)",
          "name": "type",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "fleet:create",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "fleet",
        "create.js"
      ]
    },
    "fleet": {
      "aliases": [],
      "args": {
        "fleet": {
          "description": "fleet name or slug (preferred)",
          "name": "fleet",
          "required": true
        }
      },
      "description": "Display information about a single fleet.\n\nDisplay detailed information about a single fleet.\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 fleet MyFleet",
        "$ balena fleet myorg/myfleet",
        "$ balena fleet myorg/myfleet --view"
      ],
      "flags": {
        "json": {
          "description": "Format output as json.",
          "helpGroup": "GLOBAL",
          "name": "json",
          "allowNo": false,
          "type": "boolean"
        },
        "view": {
          "description": "open fleet dashboard page",
          "name": "view",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "fleet",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": true,
      "authenticated": true,
      "primary": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "fleet",
        "index.js"
      ]
    },
    "fleet:list": {
      "aliases": [],
      "args": {},
      "description": "List all fleets.\n\nList all your balena fleets.\n\nFor detailed information on a particular fleet, use\n`balena fleet <fleet>`",
      "examples": [
        "$ balena fleet list"
      ],
      "flags": {
        "json": {
          "description": "Format output as json.",
          "helpGroup": "GLOBAL",
          "name": "json",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "fleet:list",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": true,
      "authenticated": true,
      "primary": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "fleet",
        "list.js"
      ]
    },
    "fleet:pin": {
      "aliases": [],
      "args": {
        "slug": {
          "description": "the slug of the fleet to pin to a release",
          "name": "slug",
          "required": true
        },
        "releaseToPinTo": {
          "description": "the commit of the release for the fleet to get pinned to",
          "name": "releaseToPinTo"
        }
      },
      "description": "Pin a fleet to a release.\n\nPin a fleet to a release.\n\nNote, if the commit is omitted, the currently pinned release will be printed, with instructions for how to see a list of releases",
      "examples": [
        "$ balena fleet pin myfleet",
        "$ balena fleet pin myorg/myfleet 91165e5"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "fleet:pin",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "fleet",
        "pin.js"
      ]
    },
    "fleet:purge": {
      "aliases": [],
      "args": {
        "fleet": {
          "description": "fleet name or slug (preferred)",
          "name": "fleet",
          "required": true
        }
      },
      "description": "Purge data from a fleet.\n\nPurge data from all devices belonging to a fleet.\nThis will clear the fleet's '/data' directory.\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 fleet purge MyFleet",
        "$ balena fleet purge myorg/myfleet"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "fleet:purge",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "fleet",
        "purge.js"
      ]
    },
    "fleet:rename": {
      "aliases": [],
      "args": {
        "fleet": {
          "description": "fleet name or slug (preferred)",
          "name": "fleet",
          "required": true
        },
        "newName": {
          "description": "the new name for the fleet",
          "name": "newName"
        }
      },
      "description": "Rename a fleet.\n\nRename a fleet.\n\nNote, if the `newName` parameter is omitted, it will be\nprompted for interactively.\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 fleet rename OldName",
        "$ balena fleet rename OldName NewName",
        "$ balena fleet rename myorg/oldname NewName"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "fleet:rename",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "fleet",
        "rename.js"
      ]
    },
    "fleet:restart": {
      "aliases": [],
      "args": {
        "fleet": {
          "description": "fleet name or slug (preferred)",
          "name": "fleet",
          "required": true
        }
      },
      "description": "Restart a fleet.\n\nRestart all devices belonging to a fleet.\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 fleet restart MyFleet",
        "$ balena fleet restart myorg/myfleet"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "fleet:restart",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "fleet",
        "restart.js"
      ]
    },
    "fleet:rm": {
      "aliases": [],
      "args": {
        "fleet": {
          "description": "fleet name or slug (preferred)",
          "name": "fleet",
          "required": true
        }
      },
      "description": "Remove a fleet.\n\nPermanently remove a fleet.\n\nThe --yes option may be used to avoid interactive confirmation.\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 fleet rm MyFleet",
        "$ balena fleet rm MyFleet --yes",
        "$ balena fleet rm myorg/myfleet"
      ],
      "flags": {
        "yes": {
          "char": "y",
          "description": "answer \"yes\" to all questions (non interactive use)",
          "name": "yes",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "fleet:rm",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "fleet",
        "rm.js"
      ]
    },
    "fleet:track-latest": {
      "aliases": [],
      "args": {
        "slug": {
          "description": "the slug of the fleet to make track the latest release",
          "name": "slug",
          "required": true
        }
      },
      "description": "Make this fleet track the latest release.\n\nMake this fleet track the latest release.",
      "examples": [
        "$ balena fleet track-latest myorg/myfleet",
        "$ balena fleet track-latest myfleet"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "fleet:track-latest",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "fleet",
        "track-latest.js"
      ]
    },
    "internal:osinit": {
      "aliases": [],
      "args": {
        "image": {
          "name": "image",
          "required": true
        },
        "type": {
          "name": "type",
          "required": true
        },
        "config": {
          "name": "config",
          "required": true
        }
      },
      "description": "Do actual init of the device with the preconfigured os image.\n\nDon't use this command directly!\nUse `balena os initialize <image>` instead.",
      "flags": {},
      "hasDynamicHelp": false,
      "hidden": true,
      "hiddenAliases": [],
      "id": "internal:osinit",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "root": true,
      "offlineCompatible": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "internal",
        "osinit.js"
      ]
    },
    "join": {
      "aliases": [],
      "args": {
        "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"
      ]
    },
    "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"
      ]
    },
    "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"
      ]
    },
    "logout": {
      "aliases": [],
      "args": {},
      "description": "Logout from balena.\n\nLogout from your balena account.",
      "examples": [
        "$ balena logout"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "logout",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "logout",
        "index.js"
      ]
    },
    "login": {
      "aliases": [],
      "args": {
        "token": {
          "hidden": true,
          "name": "token"
        }
      },
      "description": "Login to balena.\n\nLogin to your balena account.\n\nThis command will prompt you to login using the following login types:\n\n- Web authorization: open your web browser and prompt to authorize the CLI\nfrom the dashboard.\n\n- Credentials: using email/password and 2FA.\n\n- Token: using a session token or API key from the preferences page.",
      "examples": [
        "$ balena login",
        "$ balena login --web",
        "$ balena login --token \"...\"",
        "$ balena login --credentials",
        "$ balena login --credentials --email johndoe@gmail.com --password secret"
      ],
      "flags": {
        "web": {
          "char": "w",
          "description": "web-based login",
          "exclusive": [
            "token",
            "credentials"
          ],
          "name": "web",
          "allowNo": false,
          "type": "boolean"
        },
        "token": {
          "char": "t",
          "description": "session token or API key",
          "exclusive": [
            "web",
            "credentials"
          ],
          "name": "token",
          "allowNo": false,
          "type": "boolean"
        },
        "credentials": {
          "char": "c",
          "description": "credential-based login",
          "exclusive": [
            "web",
            "token"
          ],
          "name": "credentials",
          "allowNo": false,
          "type": "boolean"
        },
        "email": {
          "char": "e",
          "dependsOn": [
            "credentials"
          ],
          "description": "email",
          "exclusive": [
            "user"
          ],
          "name": "email",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "user": {
          "char": "u",
          "dependsOn": [
            "credentials"
          ],
          "exclusive": [
            "email"
          ],
          "hidden": true,
          "name": "user",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "password": {
          "char": "p",
          "dependsOn": [
            "credentials"
          ],
          "description": "password",
          "name": "password",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "port": {
          "char": "P",
          "dependsOn": [
            "web"
          ],
          "description": "TCP port number of local HTTP login server (--web auth only)",
          "name": "port",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "hideExperimentalWarning": {
          "char": "H",
          "description": "Hides warning for experimental features",
          "name": "hideExperimentalWarning",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "login",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "primary": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "login",
        "index.js"
      ]
    },
    "organization:list": {
      "aliases": [],
      "args": {},
      "description": "List all organizations.\n\nlist all the organizations that you are a member of.",
      "examples": [
        "$ balena organization list"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "organization:list",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "organization",
        "list.js"
      ]
    },
    "os:configure": {
      "aliases": [],
      "args": {
        "image": {
          "description": "path to a balenaOS image file, e.g. \"rpi3.img\"",
          "name": "image",
          "required": true
        }
      },
      "description": "Configure a previously downloaded balenaOS image.\n\nConfigure a previously downloaded balenaOS image for a specific device type\nor fleet.\n\nConfiguration settings such as WiFi authentication will be taken from the\nfollowing sources, in precedence order:\n1. Command-line options like `--config-wifi-ssid`\n2. A given `config.json` file specified with the `--config` option.\n3. User input through interactive prompts (text menus).\n\nThe --device-type option is used to override the fleet's default device type,\nin case of a fleet with mixed device types.\n\nThe '--dev' option is used to configure balenaOS to operate in development mode,\nallowing unauthenticated root ssh access and exposing network ports such as\nbalenaEngine's 2375 (unencrypted). This option causes `\"developmentMode\": true`\nto be inserted in the 'config.json' file in the image's boot partition. Development\nmode (as a configurable option) is applicable to balenaOS releases from early\n2022. Older releases have separate development and production balenaOS images\nthat cannot be reconfigured through 'config.json' or the '--dev' option. Do not\nconfuse the balenaOS \"development mode\" with a device's \"local mode\", the latter\nbeing a supervisor feature that allows the \"balena push\" command to push a user's\napplication directly to a device in the local network.\n\nThe '--secureBoot' option is used to configure a balenaOS installer image to opt-in\nsecure boot and disk encryption.\n\nThe --system-connection (-c) option is used to inject NetworkManager connection\nprofiles for additional network interfaces, such as cellular/GSM or additional\nWiFi or ethernet connections. This option may be passed multiple times in case there\nare multiple files to inject. See connection profile examples and reference at:\nhttps://www.balena.io/docs/reference/OS/network/2.x/\nhttps://developer.gnome.org/NetworkManager/stable/ref-settings.html\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).",
      "examples": [
        "$ balena os configure ../path/rpi3.img --device 7cf02a6",
        "$ balena os configure ../path/rpi3.img --fleet myorg/myfleet",
        "$ balena os configure ../path/rpi3.img -f myorg/myfleet --device-type raspberrypi3",
        "$ balena os configure ../path/rpi3.img --config myWifiConfig.json"
      ],
      "flags": {
        "fleet": {
          "char": "f",
          "description": "fleet name or slug (preferred)",
          "exclusive": [
            "device",
            "config"
          ],
          "name": "fleet",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "device": {
          "char": "d",
          "description": "device UUID",
          "exclusive": [
            "fleet",
            "device-type",
            "config",
            "provisioning-key-name",
            "provisioning-key-expiry-date"
          ],
          "name": "device",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "config": {
          "description": "path to a pre-generated config.json file to be injected in the OS image",
          "exclusive": [
            "fleet",
            "device",
            "advanced",
            "config-app-update-poll-interval",
            "config-network",
            "config-wifi-key",
            "config-wifi-ssid",
            "dev",
            "secureBoot",
            "device-type",
            "initial-device-name",
            "provisioning-key-name",
            "provisioning-key-expiry-date"
          ],
          "name": "config",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "advanced": {
          "char": "v",
          "description": "ask advanced configuration questions (when in interactive mode)",
          "name": "advanced",
          "allowNo": false,
          "type": "boolean"
        },
        "config-app-update-poll-interval": {
          "description": "supervisor cloud polling interval in minutes (e.g. for variable updates)",
          "name": "config-app-update-poll-interval",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "config-network": {
          "description": "device network type (non-interactive configuration)",
          "name": "config-network",
          "hasDynamicHelp": false,
          "multiple": false,
          "options": [
            "ethernet",
            "wifi"
          ],
          "type": "option"
        },
        "config-wifi-key": {
          "description": "WiFi key (password) (non-interactive configuration)",
          "name": "config-wifi-key",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "config-wifi-ssid": {
          "description": "WiFi SSID (network name) (non-interactive configuration)",
          "name": "config-wifi-ssid",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "dev": {
          "description": "Configure balenaOS to operate in development mode",
          "name": "dev",
          "allowNo": false,
          "type": "boolean"
        },
        "secureBoot": {
          "description": "Configure balenaOS installer to opt-in secure boot and disk encryption",
          "name": "secureBoot",
          "allowNo": false,
          "type": "boolean"
        },
        "device-type": {
          "dependsOn": [
            "fleet"
          ],
          "description": "device type slug (e.g. \"raspberrypi3\") to override the fleet device type",
          "name": "device-type",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "initial-device-name": {
          "description": "This option will set the device name when the device provisions",
          "name": "initial-device-name",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "provisioning-key-name": {
          "description": "custom key name assigned to generated provisioning api key",
          "exclusive": [
            "config",
            "device"
          ],
          "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)",
          "exclusive": [
            "config",
            "device"
          ],
          "name": "provisioning-key-expiry-date",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "system-connection": {
          "char": "c",
          "description": "paths to local files to place into the 'system-connections' directory",
          "name": "system-connection",
          "required": false,
          "hasDynamicHelp": false,
          "multiple": true,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "os:configure",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "os",
        "configure.js"
      ]
    },
    "os:download": {
      "aliases": [],
      "args": {
        "type": {
          "description": "the device type",
          "name": "type",
          "required": true
        }
      },
      "description": "Download an unconfigured OS image.\n\nDownload an unconfigured OS image for the specified device type.\nCheck available device types with 'balena device-type list'.\n\nNote: Currently this command only works with balenaCloud, not openBalena.\nIf using openBalena, please download the OS from: https://www.balena.io/os/\n\nThe '--version' option is used to select the balenaOS version. If omitted,\nthe latest released version is downloaded (and if only pre-release versions\nexist, the latest pre-release version is downloaded).\n\nUse '--type' to specify the type of OS download\nIf omitted, the default type for the specified device type-version combination is used.\nSome OS download types may not be available for certain device types and versions.\n\nUse '--version menu' or '--version menu-esr' to interactively select the\nOS version. The latter lists ESR versions which are only available for\ndownload on Production and Enterprise plans. See also:\nhttps://www.balena.io/docs/reference/OS/extended-support-release/\n\nDevelopment images can be selected by appending `.dev` to the version.",
      "examples": [
        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img",
        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2.101.7",
        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2022.7.0",
        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version ^2.90.0",
        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2.60.1+rev1",
        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2.60.1+rev1.dev",
        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2021.10.2.prod",
        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version latest",
        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version menu",
        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version menu-esr",
        "$ balena os download generic-amd64 -o ../foo/bar/generic-amd64.img --type installation-media"
      ],
      "flags": {
        "output": {
          "char": "o",
          "description": "output path",
          "name": "output",
          "required": true,
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "version": {
          "description": "version number (ESR or non-ESR versions),\nor semver range (non-ESR versions only),\nor 'latest' (excludes invalidated & pre-releases),\nor 'menu' (interactive menu, non-ESR versions),\nor 'menu-esr' (interactive menu, ESR versions)",
          "name": "version",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "type": {
          "description": "'disk-image' (for flashing onto device system disk/storage)\nor 'installation-media' (for creating installation media to automatically erase, format, and install balenaOS on a device)",
          "name": "type",
          "hasDynamicHelp": false,
          "multiple": false,
          "options": [
            "installation-media",
            "disk-image"
          ],
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "os:download",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "os",
        "download.js"
      ]
    },
    "os:initialize": {
      "aliases": [],
      "args": {
        "image": {
          "description": "path to OS image",
          "name": "image",
          "required": true
        }
      },
      "description": "Initialize an os image for a device.\n\n\t\tInitialize an os image for a device with a previously\n\t\tconfigured operating system image and flash the\n\t\tan external storage drive or the device's storage\n\t\tmedium depending on the device type.\n\t\t\n\nNote: Initializing the device may ask for administrative permissions\nbecause we need to access the raw devices directly.",
      "examples": [
        "$ balena os initialize ../path/rpi.img --type raspberry-pi"
      ],
      "flags": {
        "type": {
          "char": "t",
          "description": "device type (Check available types with `balena device-type list`)",
          "name": "type",
          "required": true,
          "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": "os:initialize",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "os",
        "initialize.js"
      ]
    },
    "os:versions": {
      "aliases": [],
      "args": {
        "type": {
          "description": "device type",
          "name": "type",
          "required": true
        }
      },
      "description": "Show available balenaOS versions for the given device type.\n\nShow the available balenaOS versions for the given device type.\nCheck available types with `balena device-type list`.\n\nbalenaOS ESR versions can be listed with the '--esr' option. See also:\nhttps://www.balena.io/docs/reference/OS/extended-support-release/",
      "examples": [
        "$ balena os versions raspberrypi3"
      ],
      "flags": {
        "esr": {
          "description": "select balenaOS ESR versions",
          "name": "esr",
          "allowNo": false,
          "type": "boolean"
        },
        "include-draft": {
          "description": "include pre-release balenaOS versions",
          "name": "include-draft",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "os:versions",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "os",
        "versions.js"
      ]
    },
    "push": {
      "aliases": [],
      "args": {
        "fleetOrDevice": {
          "description": "fleet name or slug, or local device IP address or \".local\" hostname",
          "name": "fleetOrDevice",
          "required": true
        }
      },
      "description": "Build release images on balenaCloud servers or on a local mode device.\n\nBuild release images on balenaCloud servers or on a local mode device.\n\nWhen building on the balenaCloud servers, the given source directory will be\nsent to the remote server. This can be used as a drop-in replacement for the\n\"git push\" deployment method.\n\nWhen building on a local mode device, the given source directory will be\nbuilt on the device, and the resulting containers will be run on the device.\nLogs will be streamed back from the device as part of the same invocation.\nThe web dashboard can be used to switch a device to local mode:\nhttps://www.balena.io/docs/learn/develop/local-mode/\nNote that local mode requires a supervisor version of at least v7.21.0.\nThe logs from only a single service can be shown with the --service flag, and\nshowing only the system logs can be achieved with --system. Note that these\nflags can be used together.\n\nWhen pushing to a local device a live session will be started.\nThe project source folder is watched for filesystem events, and changes\nto files and folders are automatically synchronized to the running\ncontainers. The synchronization is only in one direction, from this machine to\nthe device, and changes made on the device itself may be overwritten.\nThis feature requires a device running supervisor version v9.7.0 or greater.\n\nREGISTRY SECRETS  \nThe --registry-secrets option specifies a JSON or YAML file containing private\nDocker registry usernames and passwords to be used when pulling base images.\nSample registry-secrets YAML file:\n```\n\t'my-registry-server.com:25000':\n\t\tusername: ann\n\t\tpassword: hunter2\n\t'':  # Use the empty string to refer to the Docker Hub\n\t\tusername: mike\n\t\tpassword: cze14\n\t'eu.gcr.io':  # Google Container Registry\n\t\tusername: '_json_key'\n\t\tpassword: '{escaped contents of the GCR keyfile.json file}'\n```\nFor a sample project using registry secrets with the Google Container Registry,\ncheck: https://github.com/balena-io-examples/sample-gcr-registry-secrets\n\nIf the --registry-secrets option is not specified, and a secrets.yml or\nsecrets.json file exists in the balena directory (usually $HOME/.balena),\nthis file will be used instead.\n\nDOCKERIGNORE AND GITIGNORE FILES  \nBy default, the balena CLI will use a single \".dockerignore\" file (if any) at\nthe project root (--source directory) in order to decide which source files to\nexclude from the \"build context\" (tar stream) sent to balenaCloud, Docker\ndaemon or balenaEngine.  In a microservices (multicontainer) fleet, the\nsource directory is the directory that contains the \"docker-compose.yml\" file.\n\nThe --multi-dockerignore (-m) option may be used with microservices\n(multicontainer) fleets that define a docker-compose.yml file. When this\noption is used, each service subdirectory (defined by the `build` or\n`build.context` service properties in the docker-compose.yml file) is\nfiltered separately according to a .dockerignore file defined in the service\nsubdirectory. If no .dockerignore file exists in a service subdirectory, then\nonly the default .dockerignore patterns (see below) apply for that service\nsubdirectory.\n\nWhen the --multi-dockerignore (-m) option is used, the .dockerignore file (if\nany) defined at the overall project root will be used to filter files and\nsubdirectories other than service subdirectories. It will not have any effect\non service subdirectories, whether or not a service subdirectory defines its\nown .dockerignore file. Multiple .dockerignore files are not merged or added\ntogether, and cannot override or extend other files. This behavior maximizes\ncompatibility with the standard docker-compose tool, while still allowing a\nroot .dockerignore file (at the overall project root) to filter files and\nfolders that are outside service subdirectories.\n\nbalena CLI v11 also took .gitignore files into account. This behavior was\ndeprecated in CLI v12 and removed in CLI v13. Please use .dockerignore files\ninstead.\n\nDefault .dockerignore patterns  \nA few default/hardcoded dockerignore patterns are \"merged\" (in memory) with the\npatterns found in the applicable .dockerignore files, in the following order:\n```\n    **/.git\n    < user's patterns from the applicable '.dockerignore' file, if any >\n    !**/.balena\n    !**/.resin\n    !**/Dockerfile\n    !**/Dockerfile.*\n    !**/docker-compose.yml\n```\nThese patterns always apply, whether or not .dockerignore files exist in the\nproject. If necessary, the effect of the `**/.git` pattern may be modified by\nadding exception patterns to the applicable .dockerignore file(s), for example\n`!mysubmodule/.git`. For documentation on pattern format, see:\n- https://docs.docker.com/engine/reference/builder/#dockerignore-file\n- https://www.npmjs.com/package/@balena/dockerignore\n\nNote: the --service and --env flags must come after the fleetOrDevice\nparameter, as per examples.",
      "examples": [
        "$ balena push myFleet",
        "$ balena push myFleet --source <source directory>",
        "$ balena push myFleet -s <source directory>",
        "$ balena push myFleet --source <source directory> --note \"this is the note for this release\"",
        "$ balena push myFleet --release-tag key1 \"\" key2 \"value2 with spaces\"",
        "$ balena push myorg/myfleet",
        "",
        "$ balena push 10.0.0.1",
        "$ balena push 10.0.0.1 --source <source directory>",
        "$ balena push 10.0.0.1 --service my-service",
        "$ balena push 10.0.0.1 --env MY_ENV_VAR=value --env my-service:SERVICE_VAR=value",
        "$ balena push 10.0.0.1 --nolive",
        "",
        "$ balena push 23c73a1.local --system",
        "$ balena push 23c73a1.local --system --service my-service"
      ],
      "flags": {
        "source": {
          "char": "s",
          "description": "Source directory to be sent to balenaCloud or balenaOS device\n(default: current working dir)",
          "name": "source",
          "default": ".",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "emulated": {
          "char": "e",
          "description": "Don't use the faster, native balenaCloud ARM builders; force slower QEMU ARM\nemulation on Intel x86-64 builders. This flag is sometimes used to investigate\nsuspected issues with the balenaCloud backend.",
          "name": "emulated",
          "allowNo": false,
          "type": "boolean"
        },
        "dockerfile": {
          "description": "Alternative Dockerfile name/path, relative to the source folder",
          "name": "dockerfile",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "nocache": {
          "char": "c",
          "description": "Don't use cached layers of previously built images for this project. This\nensures that the latest base image and packages are pulled. Note that build\nlogs may still display the message _\"Pulling previous images for caching\npurposes\" (as the cloud builder needs previous images to compute delta\nupdates), but the logs will not display the \"Using cache\" lines for each\nbuild step of a Dockerfile.",
          "name": "nocache",
          "allowNo": false,
          "type": "boolean"
        },
        "pull": {
          "description": "When pushing to a local device, force the base images to be pulled again.\nCurrently this option is ignored when pushing to the balenaCloud builders.",
          "name": "pull",
          "allowNo": false,
          "type": "boolean"
        },
        "noparent-check": {
          "description": "Disable project validation check of 'docker-compose.yml' file in parent folder",
          "name": "noparent-check",
          "allowNo": false,
          "type": "boolean"
        },
        "registry-secrets": {
          "char": "R",
          "description": "Path to a local YAML or JSON file containing Docker registry passwords used\nto pull base images. Note that if registry-secrets are not provided on the\ncommand line, a secrets configuration file from the balena directory will be\nused (usually $HOME/.balena/secrets.yml|.json)",
          "name": "registry-secrets",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "nolive": {
          "description": "Don't run a live session on this push. The filesystem will not be monitored,\nand changes will not be synchronized to any running containers. Note that both\nthis flag and --detached are required to cause the process to end once the\ninitial build has completed.",
          "name": "nolive",
          "allowNo": false,
          "type": "boolean"
        },
        "detached": {
          "char": "d",
          "description": "When pushing to the cloud, this option will cause the build to start, then\nreturn execution back to the shell, with the status and release ID (if\napplicable).  When pushing to a local mode device, this option will cause\nthe command to not tail logs when the build has completed.",
          "name": "detached",
          "allowNo": false,
          "type": "boolean"
        },
        "service": {
          "description": "Reject logs not originating from this service.\nThis can be used in combination with --system and other --service flags.\nOnly valid when pushing to a local mode device.",
          "name": "service",
          "hasDynamicHelp": false,
          "multiple": true,
          "type": "option"
        },
        "system": {
          "description": "Only show system logs. This can be used in combination with --service.\nOnly valid when pushing to a local mode device.",
          "name": "system",
          "allowNo": false,
          "type": "boolean"
        },
        "env": {
          "description": "When performing a push to device, run the built containers with environment\nvariables provided with this argument. Environment variables can be applied\nto individual services by adding their service name before the argument,\nseparated by a colon, e.g:\n\t--env main:MY_ENV=value\nNote that if the service name cannot be found in the composition, the entire\nleft hand side of the = character will be treated as the variable name.",
          "name": "env",
          "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"
      ]
    },
    "preload": {
      "aliases": [],
      "args": {
        "image": {
          "description": "the image file path",
          "name": "image",
          "required": true
        }
      },
      "description": "Preload a release on a disk image (or Edison zip archive).\n\nPreload a release (service images/containers) from a balena fleet, and optionally\na balenaOS splash screen, in a previously downloaded '.img' balenaOS image file\nin the local disk (a zip file is only accepted for the Intel Edison device type).\nAfter preloading, the balenaOS image file can be flashed to a device's SD card.\nWhen the device boots, it will not need to download the release, as it was\npreloaded. This is usually combined with release pinning\n(https://www.balena.io/docs/learn/deploy/release-strategy/release-policy/)\nto avoid the device downloading a newer release straight away, if available.\nCheck also the Preloading and Preregistering section of the balena CLI's advanced\nmasterclass document:\nhttps://www.balena.io/docs/learn/more/masterclasses/advanced-cli/#5-preloading-and-preregistering\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).\n\nNote that the this command requires Docker to be installed, as further detailed\nin the balena CLI's installation instructions:\nhttps://github.com/balena-io/balena-cli/blob/master/INSTALL.md\nThe `--dockerHost` and `--dockerPort` flags allow a remote Docker engine to\nbe used, however the image file must be accessible to the remote Docker engine\non the same path given on the command line. This is because Docker's bind mount\nfeature is used to \"share\" the image with a container that performs the preload.",
      "examples": [
        "$ balena preload balena.img --fleet MyFleet --commit e1f2592fc6ee949e68756d4f4a48e49bff8d72a0",
        "$ balena preload balena.img --fleet myorg/myfleet --splash-image image.png",
        "$ balena preload balena.img"
      ],
      "flags": {
        "fleet": {
          "char": "f",
          "description": "fleet name or slug (preferred)",
          "name": "fleet",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "commit": {
          "char": "c",
          "description": "The commit hash of the release to preload. Use \"current\" to specify the current\nrelease (ignored if no appId is given). The current release is usually also the\nlatest, but can be pinned to a specific release. See:\nhttps://www.balena.io/docs/learn/deploy/release-strategy/release-policy/\nhttps://www.balena.io/docs/learn/more/masterclasses/fleet-management/#63-pin-using-the-api\nhttps://github.com/balena-io-examples/staged-releases",
          "name": "commit",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "splash-image": {
          "char": "s",
          "description": "path to a png image to replace the splash screen",
          "name": "splash-image",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "dont-check-arch": {
          "description": "disable architecture compatibility check between image and fleet",
          "name": "dont-check-arch",
          "allowNo": false,
          "type": "boolean"
        },
        "pin-device-to-release": {
          "char": "p",
          "description": "pin the preloaded device to the preloaded release on provision",
          "name": "pin-device-to-release",
          "allowNo": true,
          "type": "boolean"
        },
        "additional-space": {
          "description": "expand the image by this amount of bytes instead of automatically estimating the required amount",
          "name": "additional-space",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "add-certificate": {
          "description": "Add the given certificate (in PEM format) to /etc/ssl/certs in the preloading container.\nThe file name must end with '.crt' and must not be already contained in the preloader's\n/etc/ssl/certs folder.\nCan be repeated to add multiple certificates.",
          "name": "add-certificate",
          "hasDynamicHelp": false,
          "multiple": true,
          "type": "option"
        },
        "docker": {
          "char": "P",
          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
          "name": "docker",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "dockerHost": {
          "char": "h",
          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
          "name": "dockerHost",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "dockerPort": {
          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
          "name": "dockerPort",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "ca": {
          "description": "Docker host TLS certificate authority file",
          "name": "ca",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "cert": {
          "description": "Docker host TLS certificate file",
          "name": "cert",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "key": {
          "description": "Docker host TLS key file",
          "name": "key",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "preload",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "primary": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "preload",
        "index.js"
      ]
    },
    "release:finalize": {
      "aliases": [],
      "args": {
        "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"
      ]
    },
    "release-asset:delete": {
      "aliases": [],
      "args": {
        "commitOrId": {
          "description": "the commit or ID of the release",
          "name": "commitOrId",
          "required": true
        }
      },
      "description": "Delete a release asset.\n\nDelete a release asset with the specified key. This action cannot be undone.",
      "examples": [
        "$ balena release-asset delete 1234567 --key config.json",
        "$ balena release-asset delete a777f7345fe3d655c1c981aa642e5555 --key app.tar.gz",
        "$ balena release-asset delete 1234567 --key old-asset --yes"
      ],
      "flags": {
        "key": {
          "description": "the key of the release asset to delete",
          "name": "key",
          "required": true,
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "yes": {
          "char": "y",
          "description": "skip confirmation prompt",
          "name": "yes",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "release-asset:delete",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "release-asset",
        "delete.js"
      ]
    },
    "release-asset:download": {
      "aliases": [],
      "args": {
        "commitOrId": {
          "description": "the commit or ID of the release",
          "name": "commitOrId",
          "required": true
        }
      },
      "description": "Download a release asset.\n\nDownload a release asset with the specified key. By default, the file will be saved\nwith the original filename. Use the --output flag to specify a different output path.\n\nIf the output file already exists, the command will prompt for confirmation before\noverwriting, unless the --overwrite flag is specified.",
      "examples": [
        "$ balena release-asset download 1234567 --key config.json",
        "$ balena release-asset download a777f7345fe3d655c1c981aa642e5555 --key app.tar.gz --output ./downloads/app.tar.gz",
        "$ balena release-asset download 1234567 --key large-file.bin -o output.bin",
        "$ balena release-asset download 1234567 --key config.json --overwrite"
      ],
      "flags": {
        "key": {
          "description": "the key of the release asset to download",
          "name": "key",
          "required": true,
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "output": {
          "char": "o",
          "description": "output path for the downloaded file",
          "name": "output",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "overwrite": {
          "description": "overwrite existing file without confirmation",
          "name": "overwrite",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "release-asset:download",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "release-asset",
        "download.js"
      ]
    },
    "release-asset:list": {
      "aliases": [],
      "args": {
        "commitOrId": {
          "description": "the commit or ID of the release",
          "name": "commitOrId",
          "required": true
        }
      },
      "description": "List all release assets.\n\nList all assets for a specific release.",
      "examples": [
        "$ balena release-asset list 1234567",
        "$ balena release-asset list a777f7345fe3d655c1c981aa642e5555"
      ],
      "flags": {
        "json": {
          "description": "Format output as json.",
          "helpGroup": "GLOBAL",
          "name": "json",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "release-asset:list",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": true,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "release-asset",
        "list.js"
      ]
    },
    "release-asset:upload": {
      "aliases": [],
      "args": {
        "commitOrId": {
          "description": "the commit or ID of the release",
          "name": "commitOrId",
          "required": true
        },
        "filePath": {
          "description": "path to the file to upload",
          "name": "filePath",
          "required": true
        }
      },
      "description": "Upload a release asset.\n\nUpload a file as a release asset with the specified key. If the asset already exists,\nyou can use the --overwrite flag to replace it. You can customize the upload behavior with\n--chunk-size and --parallel-chunks options for larger files.",
      "examples": [
        "$ balena release-asset upload 1234567 ./path/to/config.json --key config.json",
        "$ balena release-asset upload a777f7345fe3d655c1c981aa642e5555 ./app.tar.gz --key app.tar.gz --overwrite",
        "$ balena release-asset upload 1234567 ./file.bin --key large-file.bin --chunk-size 10485760 --parallel-chunks 10"
      ],
      "flags": {
        "key": {
          "description": "the key for the release asset",
          "name": "key",
          "required": true,
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "overwrite": {
          "description": "overwrite the asset if it already exists",
          "name": "overwrite",
          "allowNo": false,
          "type": "boolean"
        },
        "chunk-size": {
          "description": "chunk size in bytes for multipart upload (minimum 5MB)",
          "name": "chunk-size",
          "default": 5242880,
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "parallel-chunks": {
          "description": "number of chunks to upload in parallel",
          "name": "parallel-chunks",
          "default": 5,
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "release-asset:upload",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "release-asset",
        "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": {
        "action": {
          "description": "enable|disable support access",
          "name": "action",
          "options": [
            "enable",
            "disable"
          ]
        }
      },
      "description": "Grant or revoke support access for devices or fleets.\n\nGrant or revoke balena support agent access to devices or fleets\non balenaCloud. (This command does not apply to openBalena.)\nAccess will be automatically revoked once the specified duration has elapsed.\n\nDuration defaults to 24h, but can be specified using --duration flag in days\nor hours, e.g. '12h', '2d'.\n\nBoth --device and --fleet flags accept multiple values, specified as\na comma-separated list (with no spaces).\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).",
      "examples": [
        "balena support enable --device ab346f,cd457a --duration 3d",
        "balena support enable --fleet myFleet --duration 12h",
        "balena support disable -f myorg/myfleet"
      ],
      "flags": {
        "device": {
          "char": "d",
          "description": "comma-separated list (no spaces) of device UUIDs",
          "name": "device",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "fleet": {
          "char": "f",
          "description": "comma-separated list (no spaces) of fleet names or slugs (preferred)",
          "name": "fleet",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "duration": {
          "char": "t",
          "description": "length of time to enable support for, in (h)ours or (d)ays, e.g. 12h, 2d",
          "name": "duration",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "support",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "support",
        "index.js"
      ]
    },
    "ssh-key:add": {
      "aliases": [],
      "args": {
        "name": {
          "description": "the SSH key name",
          "name": "name",
          "required": true
        },
        "path": {
          "description": "the path to the public key file",
          "name": "path",
          "required": true
        }
      },
      "description": "Add an SSH key to balenaCloud.\n\nAdd an SSH key to the balenaCloud account of the logged in user.\n\nIf `path` is omitted, the command will attempt to read the SSH key from stdin.\n\nAbout SSH keys\nAn \"SSH key\" actually consists of a public/private key pair. A typical name\nfor the private key file is \"id_rsa\", and a typical name for the public key\nfile is \"id_rsa.pub\". Both key files are saved to your computer (with the\nprivate key optionally protected by a password), but only the public key is\nsaved to your balena account.  This means that if you change computers or\notherwise lose the private key, you cannot recover the private key through\nyour balena account. You can however add new keys, and delete the old ones.\n\nTo generate a new SSH key pair, a nice guide can be found in GitHub's docs:\nhttps://help.github.com/en/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent\nSkip the step about adding the key to a GitHub account, and instead add it to\nyour balena account.",
      "examples": [
        "$ balena ssh-key add Main ~/.ssh/id_rsa.pub",
        "$ cat ~/.ssh/id_rsa.pub | balena ssh-key add Main",
        "# Windows 10 (cmd.exe prompt) example",
        "$ balena ssh-key add Main %userprofile%.sshid_rsa.pub"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "ssh-key:add",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "ssh-key",
        "add.js"
      ]
    },
    "ssh-key": {
      "aliases": [],
      "args": {
        "id": {
          "description": "balenaCloud ID for the SSH key",
          "name": "id",
          "required": true
        }
      },
      "description": "Display an SSH key.\n\nDisplay a single SSH key registered in balenaCloud for the logged in user.",
      "examples": [
        "$ balena ssh-key 17"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "ssh-key",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "ssh-key",
        "index.js"
      ]
    },
    "ssh-key:list": {
      "aliases": [],
      "args": {},
      "description": "List the SSH keys in balenaCloud.\n\nList all SSH keys registered in balenaCloud for the logged in user.",
      "examples": [
        "$ balena ssh-key list"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "ssh-key:list",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "ssh-key",
        "list.js"
      ]
    },
    "ssh-key:rm": {
      "aliases": [],
      "args": {
        "id": {
          "description": "balenaCloud ID for the SSH key",
          "name": "id",
          "required": true
        }
      },
      "description": "Remove an SSH key from balenaCloud.\n\nRemove a single SSH key registered in balenaCloud for the logged in user.\n\nThe --yes option may be used to avoid interactive confirmation.",
      "examples": [
        "$ balena ssh-key rm 17",
        "$ balena ssh-key rm 17 --yes"
      ],
      "flags": {
        "yes": {
          "char": "y",
          "description": "answer \"yes\" to all questions (non interactive use)",
          "name": "yes",
          "allowNo": false,
          "type": "boolean"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "ssh-key:rm",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "ssh-key",
        "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": {},
      "description": "List all tags for a fleet, device or release.\n\nList all tags and their values for the specified fleet, device or release.\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 tag list --fleet MyFleet",
        "$ balena tag list -f myorg/myfleet",
        "$ balena tag list --device 7cf02a6",
        "$ balena tag list --release 1234",
        "$ balena tag list --release b376b0e544e9429483b656490e5b9443b4349bd6"
      ],
      "flags": {
        "fleet": {
          "char": "f",
          "description": "fleet name or slug (preferred)",
          "exclusive": [
            "device",
            "release"
          ],
          "name": "fleet",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "device": {
          "char": "d",
          "description": "device UUID",
          "exclusive": [
            "fleet",
            "release"
          ],
          "name": "device",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "release": {
          "char": "r",
          "description": "release id",
          "exclusive": [
            "fleet",
            "device"
          ],
          "name": "release",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "tag:list",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "tag",
        "list.js"
      ]
    },
    "tag:rm": {
      "aliases": [],
      "args": {
        "tagKey": {
          "description": "the key string of the tag",
          "name": "tagKey",
          "required": true
        }
      },
      "description": "Remove a tag from a fleet, device or release.\n\nRemove a tag from a fleet, device or release.\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 tag rm myTagKey --fleet MyFleet",
        "$ balena tag rm myTagKey -f myorg/myfleet",
        "$ balena tag rm myTagKey --device 7cf02a6",
        "$ balena tag rm myTagKey --release 1234",
        "$ balena tag rm myTagKey --release b376b0e544e9429483b656490e5b9443b4349bd6"
      ],
      "flags": {
        "fleet": {
          "char": "f",
          "description": "fleet name or slug (preferred)",
          "exclusive": [
            "device",
            "release"
          ],
          "name": "fleet",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "device": {
          "char": "d",
          "description": "device UUID",
          "exclusive": [
            "fleet",
            "release"
          ],
          "name": "device",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "release": {
          "char": "r",
          "description": "release id",
          "exclusive": [
            "fleet",
            "device"
          ],
          "name": "release",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "tag:rm",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "missingResourceMessage": "To remove a resource tag, you must provide exactly one of:\n\n  * A fleet, with --fleet <fleetNameOrSlug>\n  * A device, with --device <UUID>\n  * A release, with --release <ID or commit>\n\nSee the help page for examples:\n\n  $ balena help tag rm",
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "tag",
        "rm.js"
      ]
    },
    "tag:set": {
      "aliases": [],
      "args": {
        "tagKey": {
          "description": "the key string of the tag",
          "name": "tagKey",
          "required": true
        },
        "value": {
          "description": "the optional value associated with the tag",
          "name": "value",
          "required": false
        }
      },
      "description": "Set a tag on a fleet, device or release.\n\nSet a tag on a fleet, device or release.\n\nYou can optionally provide a value to be associated with the created\ntag, as an extra argument after the tag key. If a value isn't\nprovided, a tag with an empty value is created.\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 tag set mySimpleTag --fleet MyFleet",
        "$ balena tag set mySimpleTag -f myorg/myfleet",
        "$ balena tag set myCompositeTag myTagValue --fleet MyFleet",
        "$ balena tag set myCompositeTag myTagValue --device 7cf02a6",
        "$ balena tag set myCompositeTag \"my tag value with whitespaces\" --device 7cf02a6",
        "$ balena tag set myCompositeTag myTagValue --release 1234",
        "$ balena tag set myCompositeTag --release 1234",
        "$ balena tag set myCompositeTag --release b376b0e544e9429483b656490e5b9443b4349bd6"
      ],
      "flags": {
        "fleet": {
          "char": "f",
          "description": "fleet name or slug (preferred)",
          "exclusive": [
            "device",
            "release"
          ],
          "name": "fleet",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "device": {
          "char": "d",
          "description": "device UUID",
          "exclusive": [
            "fleet",
            "release"
          ],
          "name": "device",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        },
        "release": {
          "char": "r",
          "description": "release id",
          "exclusive": [
            "fleet",
            "device"
          ],
          "name": "release",
          "hasDynamicHelp": false,
          "multiple": false,
          "type": "option"
        }
      },
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "tag:set",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": false,
      "enableJsonFlag": false,
      "authenticated": true,
      "missingResourceMessage": "To set a resource tag, you must provide exactly one of:\n\n  * A fleet, with --fleet <fleetNameOrSlug>\n  * A device, with --device <UUID>\n  * A release, with --release <ID or commit>\n\nSee the help page for examples:\n\n  $ balena help tag set",
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "tag",
        "set.js"
      ]
    },
    "whoami": {
      "aliases": [],
      "args": {},
      "description": "Display account information for current user.\n\nGet the username and email address of the currently logged in user.",
      "examples": [
        "$ balena whoami"
      ],
      "flags": {},
      "hasDynamicHelp": false,
      "hiddenAliases": [],
      "id": "whoami",
      "pluginAlias": "balena-cli",
      "pluginName": "balena-cli",
      "pluginType": "core",
      "strict": true,
      "enableJsonFlag": false,
      "authenticated": true,
      "isESM": false,
      "relativePath": [
        "build",
        "commands",
        "whoami",
        "index.js"
      ]
    }
  },
  "version": "24.1.3"
}