feat: Add start utilities - #9
Conversation
A command that reads from the agent starts one where nothing answers, on the next free port when something else holds the usual one, and writes the address it got down so later commands and the view agree on it. Setup starts what it installed. Asking whether it runs, and stopping it, start nothing. sourceant update replaces this command, the agent and the core, or the parts named, from the releases each is published in. Nothing is written until its checksum matches the release it came from, and a replacement is renamed over the old file, so an interrupted update leaves a working install. A machine already on a prerelease follows prereleases.
There was a problem hiding this comment.
[error] internal/command/lifecycle.go:96 (semgrep dangerous-exec-command): Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code.
Code Review SummaryCommands needing the agent now start one themselves, falling back to the next free port and persisting that address to 🚀 Key Improvements
📉 Regressions
🚨 Critical Issues
|
Any command that needs the agent starts one, on the next free port when something else holds the usual one, and writes that address down so later commands and the view agree on it. Setup starts what it installed. Status and stop start nothing.
sourceant updatereplaces this command, the agent and the core, or the parts named. Nothing is written until its checksum matches the release it came from, and a replacement is renamed over the old file, so an interrupted update leaves a working install. A machine already on a prerelease follows prereleases, which is what the beta releases need.