Files
coder/enterprise/cli/testdata/coder_agent-firewall_--help.golden
T
Sas Swart 52722b800b chore: rename boundary command to agent-firewall (#25889)
Renames the `coder boundary` CLI subcommand to `coder agent-firewall` as
part of the Boundaries → Agent Firewall rebrand.

`coder boundary` is retained as a hidden, deprecated alias that prints a
deprecation notice to stderr before running. Both commands use separate
builder functions backed by the same boundary base command and license
verification logic.

Closes https://linear.app/codercom/issue/AIGOV-236

<details><summary>Implementation notes</summary>

**Approach:** Two separate `*serpent.Command` objects (not `Aliases`) so
the deprecated `boundary` path can print a stderr warning while
`agent-firewall` stays clean.

**Changes:**
- `enterprise/cli/boundary.go`: Split old `boundary()` into
`buildAgentFirewallCmd()` and `buildBoundaryAliasCmd()`. Error messages
in `verifyLicense` now reference "agent-firewall".
- `enterprise/cli/root.go`: Register both commands.
- `cli/root.go`: Update YAML-only option validation bypass for the new
command name.
- Tests: Rename to `TestAgentFirewallSubcommand`, add
`TestBoundaryAlias`, update license verification tests to use
`agent-firewall`.
- Golden files and CLI reference docs regenerated.
- `docs/ai-coder/agent-firewall/version.md` and `docs/manifest.json`
updated.

</details>

> Generated with [Coder Agents](https://coder.com/agents) by @SasSwart
2026-06-04 11:14:36 +02:00

62 lines
2.1 KiB
Plaintext

coder v0.0.0-devel
USAGE:
coder agent-firewall [flags] [args...]
Network isolation tool for monitoring and restricting HTTP/HTTPS requests
boundary creates an isolated network environment for target processes,
intercepting HTTP/HTTPS traffic through a transparent proxy that enforces
user-defined allow rules.
OPTIONS:
--allow string, $BOUNDARY_ALLOW
Allow rule (repeatable). These are merged with allowlist from config
file. Format: "pattern" or "METHOD[,METHOD] pattern".
string-array
Allowlist rules from config file (YAML only).
--config yaml-config-path, $BOUNDARY_CONFIG
Path to YAML config file.
--disable-audit-logs bool, $DISABLE_AUDIT_LOGS
Disable sending of audit logs to the workspace agent when set to true.
--jail-type string, $BOUNDARY_JAIL_TYPE (default: nsjail)
Jail type to use for network isolation. Options: nsjail (default),
landjail.
--log-dir string, $BOUNDARY_LOG_DIR
Set a directory to write logs to rather than stderr.
--log-level string, $BOUNDARY_LOG_LEVEL (default: warn)
Set log level (error, warn, info, debug).
--log-proxy-socket-path string, $CODER_AGENT_BOUNDARY_LOG_PROXY_SOCKET_PATH (default: /tmp/boundary-audit.sock)
Path to the socket where the boundary log proxy server listens for
audit logs.
--no-user-namespace bool, $BOUNDARY_NO_USER_NAMESPACE
Do not create a user namespace. Use in restricted environments that
disallow user NS (e.g. Bottlerocket in EKS auto-mode).
--pprof bool, $BOUNDARY_PPROF
Enable pprof profiling server.
--pprof-port int, $BOUNDARY_PPROF_PORT (default: 6060)
Set port for pprof profiling server.
--proxy-port int, $PROXY_PORT (default: 8080)
Set a port for HTTP proxy.
--use-real-dns bool, $BOUNDARY_USE_REAL_DNS
Use real DNS in the jail instead of the dummy DNS (allows DNS
exfiltration). Default: false.
--version bool
Print version information and exit.
———
Run `coder --help` for a list of global options.