balena-cli 25.2.0 → 25.2.1

package/oclif.manifest.json

@@ -3209,6 +3209,30 @@
         "index.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"
+      ]
+    },
     "organization:create": {
       "aliases": [],
       "args": {
@@ -3341,27 +3365,133 @@
         "rm.js"
       ]
     },
-    "logout": {
+    "preload": {
       "aliases": [],
-      "args": {},
-      "description": "Logout from balena.\n\nLogout from your balena account.",
+      "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 logout"
+        "$ balena preload balena.img --fleet MyFleet --commit e1f2592fc6ee949e68756d4f4a48e49bff8d72a0",
+        "$ balena preload balena.img --fleet myorg/myfleet --splash-image image.png",
+        "$ balena preload balena.img"
       ],
-      "flags": {},
+      "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": "logout",
+      "id": "preload",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
+      "authenticated": true,
+      "primary": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "logout",
+        "preload",
         "index.js"
       ]
     },
@@ -3715,230 +3845,100 @@
         "versions.js"
       ]
     },
-    "preload": {
+    "push": {
       "aliases": [],
       "args": {
-        "image": {
-          "description": "the image file path",
-          "name": "image",
+        "fleetOrDevice": {
+          "description": "fleet name or slug, or local device IP address or \".local\" hostname",
+          "name": "fleetOrDevice",
           "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.",
+      "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 preload balena.img --fleet MyFleet --commit e1f2592fc6ee949e68756d4f4a48e49bff8d72a0",
-        "$ balena preload balena.img --fleet myorg/myfleet --splash-image image.png",
-        "$ balena preload balena.img"
+        "$ 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": {
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
+        "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"
         },
-        "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"
+        "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"
         },
-        "splash-image": {
-          "char": "s",
-          "description": "path to a png image to replace the splash screen",
-          "name": "splash-image",
+        "dockerfile": {
+          "description": "Alternative Dockerfile name/path, relative to the source folder",
+          "name": "dockerfile",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "dont-check-arch": {
-          "description": "disable architecture compatibility check between image and fleet",
-          "name": "dont-check-arch",
+        "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"
         },
-        "pin-device-to-release": {
-          "char": "p",
-          "description": "pin the preloaded device to the preloaded release on provision",
-          "name": "pin-device-to-release",
-          "allowNo": true,
+        "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"
         },
-        "additional-space": {
-          "description": "expand the image by this amount of bytes instead of automatically estimating the required amount",
-          "name": "additional-space",
+        "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"
         },
-        "add-certificate": {
-          "description": "Add the given certificate (in PEM format) to /etc/ssl/certs in the preloading container.\nThe file name must end with '.crt' and must not be already contained in the preloader's\n/etc/ssl/certs folder.\nCan be repeated to add multiple certificates.",
-          "name": "add-certificate",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "docker": {
-          "char": "P",
-          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
-          "name": "docker",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dockerHost": {
-          "char": "h",
-          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
-          "name": "dockerHost",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dockerPort": {
-          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
-          "name": "dockerPort",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "ca": {
-          "description": "Docker host TLS certificate authority file",
-          "name": "ca",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "cert": {
-          "description": "Docker host TLS certificate file",
-          "name": "cert",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "key": {
-          "description": "Docker host TLS key file",
-          "name": "key",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "preload",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "primary": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "preload",
-        "index.js"
-      ]
-    },
-    "push": {
-      "aliases": [],
-      "args": {
-        "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",
+        "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"
@@ -4010,41 +4010,24 @@
         "index.js"
       ]
     },
-    "release-asset:delete": {
+    "release:finalize": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release",
+          "description": "the commit or ID of the release to finalize",
           "name": "commitOrId",
           "required": true
         }
       },
-      "description": "Delete a release asset.\n\nDelete a release asset with the specified key. This action cannot be undone.",
+      "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-asset delete 1234567 --key config.json",
-        "$ balena release-asset delete a777f7345fe3d655c1c981aa642e5555 --key app.tar.gz",
-        "$ balena release-asset delete 1234567 --key old-asset --yes"
+        "$ balena release finalize a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release finalize 1234567"
       ],
-      "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"
-        }
-      },
+      "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release-asset:delete",
+      "id": "release:finalize",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -4055,194 +4038,146 @@
       "relativePath": [
         "build",
         "commands",
-        "release-asset",
-        "delete.js"
+        "release",
+        "finalize.js"
       ]
     },
-    "release-asset:download": {
+    "release": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release",
+          "description": "the commit or ID of the release to get information",
           "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.",
+      "description": "Get info for a release.",
       "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"
+        "$ balena release a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release 1234567"
       ],
       "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"
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
         },
-        "overwrite": {
-          "description": "overwrite existing file without confirmation",
-          "name": "overwrite",
+        "composition": {
+          "char": "c",
+          "description": "Return the release composition",
+          "name": "composition",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release-asset:download",
+      "id": "release",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
-      "enableJsonFlag": false,
+      "enableJsonFlag": true,
       "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "release-asset",
-        "download.js"
+        "release",
+        "index.js"
       ]
     },
-    "release-asset:list": {
+    "release:invalidate": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release",
+          "description": "the commit or ID of the release to invalidate",
           "name": "commitOrId",
           "required": true
         }
       },
-      "description": "List all release assets.\n\nList all assets for a specific release.",
+      "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-asset list 1234567",
-        "$ balena release-asset list a777f7345fe3d655c1c981aa642e5555"
+        "$ balena release invalidate a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release invalidate 1234567"
       ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
+      "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release-asset:list",
+      "id": "release:invalidate",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
-      "enableJsonFlag": true,
+      "enableJsonFlag": false,
       "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "release-asset",
-        "list.js"
+        "release",
+        "invalidate.js"
       ]
     },
-    "release-asset:upload": {
+    "release:list": {
       "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",
+        "fleet": {
+          "description": "fleet name or slug (preferred)",
+          "name": "fleet",
           "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.",
+      "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-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"
+        "$ balena release list myorg/myfleet"
       ],
       "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",
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
           "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",
+      "id": "release:list",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
-      "enableJsonFlag": false,
+      "enableJsonFlag": true,
       "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "release-asset",
-        "upload.js"
+        "release",
+        "list.js"
       ]
     },
-    "release:finalize": {
+    "release:validate": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release to finalize",
+          "description": "the commit or ID of the release to validate",
           "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.",
+      "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 finalize a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release finalize 1234567"
+        "$ balena release validate a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release validate 1234567"
       ],
       "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release:finalize",
+      "id": "release:validate",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -4254,74 +4189,101 @@
         "build",
         "commands",
         "release",
-        "finalize.js"
+        "validate.js"
       ]
     },
-    "release": {
+    "release-asset:delete": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release to get information",
+          "description": "the commit or ID of the release",
           "name": "commitOrId",
           "required": true
         }
       },
-      "description": "Get info for a release.",
+      "description": "Delete a release asset.\n\nDelete a release asset with the specified key. This action cannot be undone.",
       "examples": [
-        "$ balena release a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release 1234567"
+        "$ 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": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
+        "key": {
+          "description": "the key of the release asset to delete",
+          "name": "key",
+          "required": true,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         },
-        "composition": {
-          "char": "c",
-          "description": "Return the release composition",
-          "name": "composition",
+        "yes": {
+          "char": "y",
+          "description": "skip confirmation prompt",
+          "name": "yes",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release",
+      "id": "release-asset:delete",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
-      "enableJsonFlag": true,
+      "enableJsonFlag": false,
       "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "release",
-        "index.js"
+        "release-asset",
+        "delete.js"
       ]
     },
-    "release:invalidate": {
+    "release-asset:download": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release to invalidate",
+          "description": "the commit or ID of the release",
           "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.",
+      "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 invalidate a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release invalidate 1234567"
+        "$ 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": {},
+      "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:invalidate",
+      "id": "release-asset:download",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -4332,22 +4294,23 @@
       "relativePath": [
         "build",
         "commands",
-        "release",
-        "invalidate.js"
+        "release-asset",
+        "download.js"
       ]
     },
-    "release:list": {
+    "release-asset:list": {
       "aliases": [],
       "args": {
-        "fleet": {
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
+        "commitOrId": {
+          "description": "the commit or ID of the release",
+          "name": "commitOrId",
           "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).",
+      "description": "List all release assets.\n\nList all assets for a specific release.",
       "examples": [
-        "$ balena release list myorg/myfleet"
+        "$ balena release-asset list 1234567",
+        "$ balena release-asset list a777f7345fe3d655c1c981aa642e5555"
       ],
       "flags": {
         "json": {
@@ -4360,7 +4323,7 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release:list",
+      "id": "release-asset:list",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -4371,28 +4334,65 @@
       "relativePath": [
         "build",
         "commands",
-        "release",
+        "release-asset",
         "list.js"
       ]
     },
-    "release:validate": {
+    "release-asset:upload": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release to validate",
+          "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": "Validate a release.\n\nValidate a release.\n\nValid releases are automatically deployed to devices tracking the latest\nrelease if they are finalized.",
+      "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 validate a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release validate 1234567"
+        "$ 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": {},
+      "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:validate",
+      "id": "release-asset:upload",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -4403,8 +4403,8 @@
       "relativePath": [
         "build",
         "commands",
-        "release",
-        "validate.js"
+        "release-asset",
+        "upload.js"
       ]
     },
     "settings": {
@@ -4895,5 +4895,5 @@
       ]
     }
   },
-  "version": "25.2.0"
+  "version": "25.2.1"
 }