studio/cli
2
0
Fork 0
Code Issues Pull Requests Actions Packages Releases 4 Wiki Activity
Files
27a6f4377cab8c339b9e8fc01689e3a246324d04
cli/Cargo.toml

98 lines
2.2 KiB
TOML
Raw Normal View History

feat(wfe): integrate workflow engine for up, seed, verify, bootstrap Dispatch `sunbeam up`, `sunbeam seed`, `sunbeam verify`, and `sunbeam bootstrap` through WFE workflows instead of monolithic functions. Steps communicate via JSON workflow data and each workflow is persisted in a per-context SQLite database.
2026-04-05 18:21:59 +01:00
[package]
name = "sunbeam"
version = "1.1.2"
edition = "2024"
description = "Sunbeam Studios CLI"
repository = "https://src.sunbeam.pt/studio/cli"
license = "MIT"
[[bin]]
name = "sunbeam"
path = "src/main.rs"
refactor: workspace scaffolding — sunbeam-sdk + sunbeam binary crate Convert the single binary crate into a Cargo workspace with two members: sunbeam-sdk (library) and sunbeam (thin binary). Moves build.rs to the SDK with adjusted .git/HEAD path for the nested layout.
2026-03-21 14:34:15 +00:00
[workspace]
feat(net): scaffold sunbeam-net crate with foundations Add the workspace crate that will host a pure Rust Headscale/Tailscale- compatible VPN client. This first commit lands the crate skeleton plus the leaf modules that the rest of the stack builds on: - error: thiserror Error enum + Result alias - config: VpnConfig - keys: Curve25519 node/disco/wg key types with on-disk persistence - proto/types: PascalCase serde wire types matching Tailscale's JSON
2026-04-07 13:40:27 +01:00
members = ["sunbeam-sdk", "sunbeam-net"]
refactor: workspace scaffolding — sunbeam-sdk + sunbeam binary crate Convert the single binary crate into a Cargo workspace with two members: sunbeam-sdk (library) and sunbeam (thin binary). Moves build.rs to the SDK with adjusted .git/HEAD path for the nested layout.
2026-03-21 14:34:15 +00:00
resolver = "3"
feat(wfe): integrate workflow engine for up, seed, verify, bootstrap Dispatch `sunbeam up`, `sunbeam seed`, `sunbeam verify`, and `sunbeam bootstrap` through WFE workflows instead of monolithic functions. Steps communicate via JSON workflow data and each workflow is persisted in a per-context SQLite database.
2026-04-05 18:21:59 +01:00
[dependencies]
feat(cli): wire sunbeam-net into sunbeam connect/disconnect/vpn Adds the foreground VPN client commands. The daemon runs in-process inside the CLI for the lifetime of `sunbeam connect` — no separate background daemon yet, that can come later if needed. - Cargo.toml: add sunbeam-net as a workspace dep, plus hostname/whoami for building a per-machine netmap label like "sienna@laptop" - src/config.rs: new `vpn-url` and `vpn-auth-key` fields on Context - src/cli.rs: `Connect`, `Disconnect`, and `Vpn { Status }` verbs - src/vpn_cmds.rs: command handlers - cmd_connect reads VPN config from the active context, starts the daemon at ~/.sunbeam/vpn, polls for Running, then blocks on ^C before calling DaemonHandle::shutdown - cmd_disconnect / cmd_vpn_status are placeholders that report based on the control socket; actually talking to a backgrounded daemon needs an IPC client (not yet exposed from sunbeam-net) - src/workflows/mod.rs: `..Default::default()` on Context literals so the new fields don't break the existing tests
2026-04-07 14:39:40 +01:00
# Workspace
sunbeam-sdk = { path = "sunbeam-sdk" }
sunbeam-net = { path = "sunbeam-net" }
feat(wfe): integrate workflow engine for up, seed, verify, bootstrap Dispatch `sunbeam up`, `sunbeam seed`, `sunbeam verify`, and `sunbeam bootstrap` through WFE workflows instead of monolithic functions. Steps communicate via JSON workflow data and each workflow is persisted in a per-context SQLite database.
2026-04-05 18:21:59 +01:00
# Core
thiserror = "2"
tokio = { version = "1", features = ["full"] }
clap = { version = "4", features = ["derive"] }
serde = { version = "1", features = ["derive"] }
serde_json = "1"
serde_yaml = "0.9"
tracing = "0.1"
tracing-subscriber = { version = "0.3", features = ["env-filter"] }
rustls = { version = "0.23", features = ["ring"] }
# Kubernetes
kube = { version = "0.99", features = ["client", "runtime", "derive", "ws"] }
k8s-openapi = { version = "0.24", features = ["v1_32"] }
# HTTP + TLS
reqwest = { version = "0.12", default-features = false, features = ["json", "rustls-tls"] }
bytes = "1"
# SSH
russh = "0.46"
russh-keys = "0.46"
# Crypto
rsa = "0.9"
pkcs8 = { version = "0.10", features = ["pem"] }
pkcs1 = { version = "0.7", features = ["pem"] }
sha2 = "0.10"
hmac = "0.12"
base64 = "0.22"
rand = "0.8"
aes-gcm = "0.10"
argon2 = "0.5"
indicatif = { version = "0.17", features = ["tokio"] }
# Certificate generation
rcgen = "0.14"
# SMTP
lettre = { version = "0.11", default-features = false, features = ["smtp-transport", "tokio1-rustls-tls", "builder", "hostname"] }
# Archive handling
flate2 = "1"
tar = "0.4"
# Async
futures = "0.3"
tokio-stream = "0.1"
# Utility
tempfile = "3"
dirs = "5"
chrono = { version = "0.4", features = ["serde"] }
refactor(openbao): migrate to vaultrs client library Replace hand-rolled OpenBao HTTP client with vaultrs 0.8.0, which has official OpenBao support. BaoClient remains the public API so callers are unchanged. KV patch uses raw HTTP since vaultrs doesn't expose it yet.
2026-04-05 22:34:41 +01:00
# OpenBao/Vault client
vaultrs = "0.8"
feat(wfe): integrate workflow engine for up, seed, verify, bootstrap Dispatch `sunbeam up`, `sunbeam seed`, `sunbeam verify`, and `sunbeam bootstrap` through WFE workflows instead of monolithic functions. Steps communicate via JSON workflow data and each workflow is persisted in a per-context SQLite database.
2026-04-05 18:21:59 +01:00
# Workflow engine
fix(wfe): update to 1.6.3 for step name display in print_summary WFE now populates execution pointer step_name from the workflow definition, so print_summary shows actual step names instead of "step-0", "step-1", etc.
2026-04-05 20:09:32 +01:00
wfe = { version = "1.6.3", registry = "sunbeam" }
wfe-core = { version = "1.6.3", registry = "sunbeam", features = ["test-support"] }
wfe-sqlite = { version = "1.6.3", registry = "sunbeam" }
wfe-yaml = { version = "1.6.3", registry = "sunbeam" }
feat(wfe): integrate workflow engine for up, seed, verify, bootstrap Dispatch `sunbeam up`, `sunbeam seed`, `sunbeam verify`, and `sunbeam bootstrap` through WFE workflows instead of monolithic functions. Steps communicate via JSON workflow data and each workflow is persisted in a per-context SQLite database.
2026-04-05 18:21:59 +01:00
async-trait = "0.1"
feat(cli): wire sunbeam-net into sunbeam connect/disconnect/vpn Adds the foreground VPN client commands. The daemon runs in-process inside the CLI for the lifetime of `sunbeam connect` — no separate background daemon yet, that can come later if needed. - Cargo.toml: add sunbeam-net as a workspace dep, plus hostname/whoami for building a per-machine netmap label like "sienna@laptop" - src/config.rs: new `vpn-url` and `vpn-auth-key` fields on Context - src/cli.rs: `Connect`, `Disconnect`, and `Vpn { Status }` verbs - src/vpn_cmds.rs: command handlers - cmd_connect reads VPN config from the active context, starts the daemon at ~/.sunbeam/vpn, polls for Running, then blocks on ^C before calling DaemonHandle::shutdown - cmd_disconnect / cmd_vpn_status are placeholders that report based on the control socket; actually talking to a backgrounded daemon needs an IPC client (not yet exposed from sunbeam-net) - src/workflows/mod.rs: `..Default::default()` on Context literals so the new fields don't break the existing tests
2026-04-07 14:39:40 +01:00
hostname = "0.4.2"
whoami = "2.1.1"
feat(cli): background the VPN daemon with re-exec + clean shutdown `sunbeam connect` now fork-execs itself with a hidden `__vpn-daemon` subcommand instead of running the daemon in-process. The user-facing command spawns the child detached (stdio → log file, setsid for no controlling TTY), polls the IPC socket until the daemon reaches Running, prints a one-line status, and exits. The user gets back to their shell immediately. - src/cli.rs: `Connect { foreground }` instead of unit. Add hidden `__vpn-daemon` Verb that the spawned child runs. - src/vpn_cmds.rs: split into spawn_background_daemon (default path) and run_daemon_foreground (used by both `connect --foreground` and `__vpn-daemon`). Detached child uses pre_exec(setsid) and inherits --context from the parent so it resolves the same VPN config. Refuses to start if a daemon is already running on the control socket; cleans up stale socket files. Switches the proxy bind from 16443 (sienna's existing SSH tunnel uses it) to 16579. - sunbeam-net/src/daemon/lifecycle: add a SocketGuard RAII type so the IPC control socket is unlinked when the daemon exits, regardless of shutdown path. Otherwise `vpn status` after a clean disconnect would see a stale socket and report an error. End-to-end smoke test against the docker stack: $ sunbeam connect ==> VPN daemon spawned (pid 90072, ...) Connected (100.64.0.154, fd7a:115c:a1e0::9a) — 2 peers visible $ sunbeam vpn status VPN: running addresses: 100.64.0.154, fd7a:115c:a1e0::9a peers: 2 derp home: region 0 $ sunbeam disconnect ==> Asking VPN daemon to stop... Daemon acknowledged shutdown. $ sunbeam vpn status VPN: not running
2026-04-07 14:57:15 +01:00
libc = "0.2.184"
feat(wfe): integrate workflow engine for up, seed, verify, bootstrap Dispatch `sunbeam up`, `sunbeam seed`, `sunbeam verify`, and `sunbeam bootstrap` through WFE workflows instead of monolithic functions. Steps communicate via JSON workflow data and each workflow is persisted in a per-context SQLite database.
2026-04-05 18:21:59 +01:00
[dev-dependencies]
wiremock = "0.6"
[build-dependencies]
reqwest = { version = "0.12", default-features = false, features = ["blocking", "rustls-tls"] }
sha2 = "0.10"
flate2 = "1"
tar = "0.4"
chrono = "0.4"
Reference in New Issue Copy Permalink