Merge branch 'main' into cursor-rules

Author: mangelajo

.github/workflows/trigger-packages-index.yaml

@@ -18,6 +18,9 @@ jobs:
         with:
           app-id: ${{ secrets.JUMPSTARTER_BACKPORT_BOT_APP_ID }}
           private-key: ${{ secrets.JUMPSTARTER_BACKPORT_BOT_PRIVATE_KEY }}
+          owner: ${{ github.repository_owner }}
+          repositories: |
+            packages
 
       - name: Trigger packages repository index generation
         uses: peter-evans/repository-dispatch@v3

Makefile

@@ -8,7 +8,7 @@ help:
 	@echo ""
 	@echo "Build targets:"
 	@echo "  build              - Build all packages"
-	@echo "  generate           - Generate code from protobuf definitions"
+	@echo "  protobuf-gen       - Generate code from protobuf definitions"
 	@echo "  sync               - Sync all packages and extras"
 	@echo ""
 	@echo "Documentation targets:"
@@ -75,8 +75,18 @@ pkg-ty-all: $(addprefix pkg-ty-,$(PKG_TARGETS))
 build:
 	uv build --all --out-dir dist
 
-generate:
-	buf generate
+protobuf-gen:
+	podman run --volume "$(shell pwd):/workspace" --workdir /workspace docker.io/bufbuild/buf:latest generate
+	# Fix Python imports: convert absolute imports to relative imports
+	# In jumpstarter/client/v1: from jumpstarter.v1 import -> from ...v1 import
+	find packages/jumpstarter-protocol/jumpstarter_protocol/jumpstarter/client/v1 -name "*_pb2*.py" -type f -exec sed -i.bak \
+		-e 's|^from jumpstarter\.v1 import|from ...v1 import|g' \
+		-e 's|^from jumpstarter\.client\.v1 import|from . import|g' \
+		{} \; -exec rm {}.bak \;
+	# In jumpstarter/v1: from jumpstarter.v1 import -> from . import
+	find packages/jumpstarter-protocol/jumpstarter_protocol/jumpstarter/v1 -name "*_pb2*.py" -type f -exec sed -i.bak \
+		-e 's|^from jumpstarter\.v1 import|from . import|g' \
+		{} \; -exec rm {}.bak \;
 
 sync:
 	uv sync --all-packages --all-extras

README.md

@@ -34,9 +34,9 @@ pip install --extra-index-url https://pkg.jumpstarter.dev/ jumpstarter-cli
 ```
 
 To install the [Jumpstarter
-Service](https://jumpstarter.dev/introduction/service.html) in your Kubernetes
+Service](https://jumpstarter.dev/main/introduction/service.html) in your Kubernetes
 cluster, see the [Service
-Installation](https://jumpstarter.dev/installation/service/index.html)
+Installation](https://jumpstarter.dev/main/getting-started/installation/index.html)
 documentation.
 
 ## Documentation
@@ -51,7 +51,7 @@ Additionally, the command line reference documentation can be viewed with `jmp
 
 Jumpstarter welcomes contributors of all levels of experience and would love to
 see you involved in the project. See the [contributing
-guide](https://jumpstarter.dev/contributing/) to get started.
+guide](https://jumpstarter.dev/main/contributing.html) to get started.
 
 ## License
 

buf.gen.yaml

@@ -8,4 +8,5 @@ plugins:
     out: ./packages/jumpstarter-protocol/jumpstarter_protocol
 inputs:
   - git_repo: https://github.com/jumpstarter-dev/jumpstarter-protocol.git
+    branch: main
     subdir: proto

docs/source/conf.py

@@ -10,7 +10,7 @@
 import os
 import sys
 
-from jumpstarter_cli_admin.controller import get_latest_compatible_controller_version
+from jumpstarter_kubernetes.controller import get_latest_compatible_controller_version
 
 os.environ["TERM"] = "dumb"
 
@@ -32,7 +32,7 @@
     "sphinx_click",
     "sphinx_substitution_extensions",
     "sphinx_copybutton",
-    "sphinx_inline_tabs"
+    "sphinx_inline_tabs",
 ]
 
 templates_path = ["_templates"]

docs/source/getting-started/guides/setup-distributed-mode.md

@@ -4,7 +4,7 @@ This guide walks you through the process of creating an exporter using the
 controller service, configuring drivers, and running the exporter.
 
 ```{warning}
-The jumpstarter-controller endpoints are secured by TLS. However, in release 0.6.x,
+The jumpstarter-controller endpoints are secured by TLS. However, in release 0.7.x,
 the certificates are self-signed and rotated on every restart. This means the client
 will not be able to verify the server certificate. To bypass this, you should use the
 `--insecure-tls-config` flag when creating clients and exporters. This issue will be

docs/source/getting-started/installation/packages.md

@@ -38,8 +38,8 @@ If you have the repository cloned locally:
 
 | Installation Type | Command | Description |
 |------------------|---------|-------------|
-| Stable release (recommended) | `./install.sh` | Install stable release 0.6 |
-| Stable release (explicit) | `./install.sh -s release-0.6` | Install stable release 0.6 explicitly |
+| Stable release (recommended) | `./install.sh` | Install stable release 0.7 |
+| Stable release (explicit) | `./install.sh -s release-0.7` | Install stable release 0.7 explicitly |
 | Development version | `./install.sh -s main` | Install latest development version |
 | Release candidate | `./install.sh -s rc` | Install latest release candidate (when available) |
 | Custom directory | `./install.sh -d /opt/jumpstarter` | Install to custom directory |
@@ -73,7 +73,7 @@ echo 'source ~/.local/jumpstarter/set' >> ~/.bashrc
 
 | Option | Description | Default |
 |--------|-------------|---------|
-| `-s, --source SOURCE` | Installation source (release-0.6, latest, rc, main) | `release-0.6` |
+| `-s, --source SOURCE` | Installation source (release-0.7, latest, rc, main) | `release-0.7` |
 | `-d, --dir DIR` | Installation directory | `~/.local/jumpstarter` |
 | `-h, --help` | Show help message | - |
 
@@ -165,7 +165,7 @@ indexes:
 | ------------------------------------------------------ | --------------------------------------------------------------------- |
 | [releases](https://pkg.jumpstarter.dev/)               | Release, or release-candidate versions                                |
 | [main](https://pkg.jumpstarter.dev/main/)              | Index tracking the main branch, equivalent to installing from sources |
-| [release-0.6](https://pkg.jumpstarter.dev/release-0.6) | Index tracking a stable branch                                        |
+| [release-0.7](https://pkg.jumpstarter.dev/release-0.7) | Index tracking a stable branch                                        |
 
 #### Installing from Source
 

docs/source/getting-started/installation/service/service-local.md

@@ -13,9 +13,13 @@ Before installing locally, ensure you have:
 
 ## Install with Jumpstarter CLI
 
-The Jumpstarter CLI provides the `jmp admin install` command to automatically
-run Helm with the correct arguments, simplifying installation in your Kubernetes
-cluster. This is the recommended approach for getting started quickly.
+The Jumpstarter CLI provides convenient commands for local demo/test cluster management and Jumpstarter installation:
+
+- `jmp admin create cluster` - Creates a local cluster and installs Jumpstarter (recommended for getting started quickly)
+- `jmp admin delete cluster` - Deletes a local cluster completely
+- `jmp admin get clusters` - Get local clusters from a Kubeconfig
+- `jmp admin install` - Installs Jumpstarter on an existing cluster
+- `jmp admin uninstall` - Removes Jumpstarter from a cluster (but keeps the cluster)
 
 ```{warning}
 Sometimes the automatic IP address detection for will not work correctly, to check if Jumpstarter can determine your IP address, run `jmp admin ip`. If the IP address cannot be determined, use the `--ip` argument to manually set your IP address.
@@ -27,44 +31,65 @@ If you want to test Jumpstarter locally with more control over the setup, you ca
 
 [**kind**](https://kind.sigs.k8s.io/docs/user/quick-start/) (Kubernetes in Docker) is a tool for running local Kubernetes clusters using Docker or Podman containerized "nodes". It's lightweight and fast to start, making it excellent for CI/CD pipelines and quick local testing.
 
-[**minikube**](https://minikube.sigs.k8s.io/docs/start/) runs local Kubernetes clusters using VMs or container "nodes". It works across several platforms and supports different hypervisors, making it ideal for local development and testing. It's particularly useful in environments requiring untrusted certificates.
+[**minikube**](https://minikube.sigs.k8s.io/docs/start/) runs local Kubernetes clusters using VMs or container "nodes". It works across several platforms and supports different hypervisors, making it ideal for local development and testing. Minikube works better if you don't have a local Docker/Podman installation.
+
+The admin CLI can automatically create a local cluster and install Jumpstarter with a single command:
+
+By default, Jumpstarter will try to detect which local cluster tools are installed:
 
 ```{tip}
-Consider minikube for environments requiring [untrusted certificates](https://minikube.sigs.k8s.io/docs/handbook/untrusted_certs/).
+By default, Jumpstarter will use `kind` if available, use the `--minikube` argument to force Jumpstarter to use minikube instead.
 ```
 
-The admin CLI can automatically create a local cluster and install Jumpstarter with a single command:
+```{code-block} console
+$ jmp admin create cluster
+```
+
+However, you can also explicitly specify a local cluster tool:
 
 ````{tab} kind
 ```{code-block} console
-$ jmp admin install --kind --create-cluster
+$ jmp admin create cluster --kind
 ```
+
+Additional options for cluster creation:
+
+- Custom cluster name: Specify as the first argument (default: `jumpstarter-lab`)
+- `--kind <PATH>`: Path to the kind binary to use for cluster management
+- `--helm <PATH>`: Path to the Helm binary to install the Jumpstarter service with
+- `--force-recreate`: Force recreate the cluster if it already exists (destroys all data)
+- `--kind-extra-args`: Pass additional arguments to kind cluster creation
+- `--skip-install`: Create the cluster without installing Jumpstarter
+- `--extra-certs <PATH>`: Path to custom CA certificate bundle file to inject into the cluster
 ````
 
 ````{tab} minikube
 ```{code-block} console
-$ jmp admin install --minikube --create-cluster
+$ jmp admin create cluster --minikube
 ```
-````
 
 Additional options for cluster creation:
 
-- `--cluster-name`: Specify a custom cluster name (default: `jumpstarter-lab`)
-- `--force-recreate-cluster`: Force recreate the cluster if it already exists (destroys all data)
-- `--kind-extra-args`: Pass additional arguments to kind cluster creation
+- Custom cluster name: Specify as the first argument (default: `jumpstarter-lab`)
+- `--minikube <PATH>`: Path to the minikube binary to use for cluster management
+- `--helm <PATH>`: Path to the Helm binary to install the Jumpstarter service with
+- `--force-recreate`: Force recreate the cluster if it already exists (destroys all data)
 - `--minikube-extra-args`: Pass additional arguments to minikube cluster creation
+- `--skip-install`: Create the cluster without installing Jumpstarter
+- `--extra-certs <PATH>`: Path to custom CA certificate bundle file to inject into the cluster
+````
 
 To set a custom cluster name:
 
 ````{tab} kind
 ```{code-block} console
-$ jmp admin install --kind --create-cluster --cluster-name my-jumpstarter-cluster
+$ jmp admin create cluster my-jumpstarter-cluster --kind
 ```
 ````
 
 ````{tab} minikube
 ```{code-block} console
-$ jmp admin install --minikube --create-cluster --cluster-name my-jumpstarter-cluster
+$ jmp admin create cluster my-jumpstarter-cluster --minikube
 ```
 ````
 
@@ -90,28 +115,41 @@ $ jmp admin install --minikube
 
 ### Uninstall Jumpstarter
 
-Uninstall Jumpstarter with the CLI:
+Uninstall Jumpstarter from the cluster with the CLI:
 
 ```{code-block} console
 $ jmp admin uninstall
 ```
 
-To delete the local cluster when uninstalling, use the `--delete-cluster` flag:
+To delete the local cluster completely, use the cluster delete command:
+
+````{tab} kind
+```{code-block} console
+$ jmp admin delete cluster --kind
+```
+````
+
+````{tab} minikube
+```{code-block} console
+$ jmp admin delete cluster --minikube
+```
+````
+
+To delete a cluster with a custom name:
 
 ````{tab} kind
 ```{code-block} console
-$ jmp admin uninstall --kind --delete-cluster
+$ jmp admin delete cluster my-jumpstarter-cluster --kind
 ```
 ````
 
 ````{tab} minikube
 ```{code-block} console
-$ jmp admin uninstall --minikube --delete-cluster
+$ jmp admin delete cluster my-jumpstarter-cluster --minikube
 ```
 ````
 
-For complete documentation of the `jmp admin install` command and all available
-options, see the [MAN pages](../../../reference/man-pages/jmp.md).
+For complete documentation of the `jmp admin create cluster`, `jmp admin delete cluster`, `jmp admin get clusters`, and `jmp admin install` commands and all available options, see the [MAN pages](../../../reference/man-pages/jmp.md).
 
 ## Manual Local Cluster Install
 

docs/source/reference/package-apis/drivers/ble.md

@@ -0,0 +1 @@
+../../../../../packages/jumpstarter-driver-ble/README.md

docs/source/reference/package-apis/drivers/index.md

@@ -30,6 +30,7 @@ Drivers that control the power state and basic operation of devices:
 
 Drivers that provide various communication interfaces:
 
+* **[BLE](ble.md)** (`jumpstarter-driver-ble`) - Bluetooth Low Energy communication
 * **[CAN](can.md)** (`jumpstarter-driver-can`) - Controller Area Network
   communication
 * **[HTTP](http.md)** (`jumpstarter-driver-http`) - HTTP communication
@@ -79,9 +80,12 @@ Drivers for debugging and programming devices:
 General-purpose utility drivers:
 
 * **[Shell](shell.md)** (`jumpstarter-driver-shell`) - Shell command execution
+* **[TMT](tmt.md)** (`jumpstarter-driver-tmt`) - TMT (Test Management Tool) wrapper driver
+* **[SSH](ssh.md)** (`jumpstarter-driver-ssh`) - SSH wrapper driver
 
 ```{toctree}
 :hidden:
+ble.md
 can.md
 corellium.md
 dutlink.md
@@ -100,8 +104,10 @@ gpiod.md
 ridesx.md
 sdwire.md
 shell.md
+ssh.md
 snmp.md
 tasmota.md
+tmt.md
 tftp.md
 uboot.md
 ustreamer.md