Operator guide for Valet Dedicated 0.10.1
Service operations
Use the operator tool to inventory services and stop traffic during an
incident. The same controls appear at /admin/services on the dashboard.
Sign in with a superuser account to use that page.
Inventory
List every service, or filter by org and kind:
valet-dedicated services list
valet-dedicated services list --org acme --kind app
valet-dedicated services list --output jsonKinds are site, app, agent, and skill. The CLI follows every page.
JSON output contains one object per line. Each row includes org and service
IDs, name, kind, access, connectors, last publisher, publication time, and
suspension details. Missing publisher or publication time means none is
recorded. Existing services use their active release's update time as the
initial publication timestamp.
Suspend
Suspend a named service with an audit reason:
valet-dedicated services suspend acme/help --reason "incident containment"Suspend every existing service, optionally within one org:
valet-dedicated services suspend --all --reason "incident containment"
valet-dedicated services suspend --all --org acme --reason "incident containment" --yesBulk actions ask for confirmation. Pass --yes for an unattended command.
An empty reason is refused. Services created after the bulk action remain
active.
Suspension immediately refuses new HTTP traffic with service.suspended.
Processes stop through normal convergence. Existing connections may finish
before teardown. Org members cannot publish, deploy, or scale suspended
services. Suspension survives reconciler loops and process restarts.
Resume
Resume restores the saved formation and access:
valet-dedicated services resume acme/help --reason "incident resolved"
valet-dedicated services resume --all --org acme --reason "incident resolved" --yesResume also accepts --all without --org. It prompts for bulk changes.
Without --reason, it records operator requested resume. Repeating either
transition is safe. A previously stopped service stays stopped; an idle agent
stays idle. Container startup completes asynchronously.
Each request records its actor, target, reason, and admission outcome in the audit log. The CLI authenticates with the installation's operator token. It uses the same service suspension implementation as Valet Cloud.