docs: add juno snapshot upload to CLI (#547)

* docs: juno snapshot upload to CLI

Signed-off-by: David Dal Busco <david.dalbusco@outlook.com>

* 📄 Update LLMs.txt snapshot for PR review

---------

Signed-off-by: David Dal Busco <david.dalbusco@outlook.com>
Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

Author: peterpeterparker

.llms-snapshots/llms-full.txt

@@ -7765,6 +7765,16 @@ Usage: juno snapshot <subcommand> [options]Subcommands:  create               Cr
 
 ---
 
+### Upload
+
+Upload a snapshot from offline files.
+
+```
+Usage: juno snapshot upload [options]Options:  --dir                 Path to the snapshot directory that contains the metadata.json and chunks.  -t, --target          Which module type should be snapshotted? Valid targets are satellite, mission-control or orbiter.  --target-id           The module ID of a specific target to upload the snapshot to.  -m, --mode            Choose which environment to use (production, staging, development). Defaults to production if omitted.  -p, --profile         Specify an optional profile to use (e.g. personal, team). Useful when managing multiple Mission Controls.  --container-url       Override a custom container URL. If not provided, defaults to production or the local container in development mode.  --console-url         Specify a custom URL to access the developer Console.  -h, --help            Output usage information.Notes:- Targets can be shortened to s for satellite, m for mission-control and o for orbiter.
+```
+
+---
+
 ### Stop
 
 Stop a module.

docs/reference/cli.mdx

@@ -153,6 +153,14 @@ import Snapshot from "./cli/snapshot.md";
 
 ---
 
+### Upload
+
+import SnapshotUpload from "./cli/snapshot-upload.md";
+
+<SnapshotUpload />
+
+---
+
 ### Stop
 
 import Stop from "./cli/stop.md";

docs/reference/cli/snapshot-upload.md

@@ -0,0 +1,19 @@
+Upload a snapshot from offline files.
+
+```
+Usage: juno snapshot upload [options]
+
+Options:
+  --dir                 Path to the snapshot directory that contains the metadata.json and chunks.
+  -t, --target          Which module type should be snapshotted? Valid targets are satellite, mission-control or orbiter.
+  --target-id           The module ID of a specific target to upload the snapshot to.
+  -m, --mode            Choose which environment to use (production, staging, development). Defaults to production if omitted.
+  -p, --profile         Specify an optional profile to use (e.g. personal, team). Useful when managing multiple Mission Controls.
+  --container-url       Override a custom container URL. If not provided, defaults to production or the local container in development mode.
+  --console-url         Specify a custom URL to access the developer Console.
+  -h, --help            Output usage information.
+
+Notes:
+
+- Targets can be shortened to s for satellite, m for mission-control and o for orbiter.
+```

scripts/cli-to-md.sh

@@ -43,4 +43,10 @@ for cmd in $(echo $CONFIG_COMMANDS | sed "s/,/ /g"); do
   generate_command_markdown "config $cmd"
 done
 
+EMULATOR_COMMANDS=upload
+
+for cmd in $(echo $EMULATOR_COMMANDS | sed "s/,/ /g"); do
+  generate_command_markdown "snapshot $cmd"
+done
+
 npm run format