Current state
Only psa domain status --report pushes status to PSA-OPS (via _report_status_to_api at src/psa/commands/domain.py:171). Lifecycle commands (start, stop, restart, bounce, kill, configure, purge, flush) execute the action and exit without updating PSA-OPS. Users have to follow up with psa domain status --report to sync.
Desired
After each lifecycle command's success, send the resulting status to PSA-OPS automatically. Reuse _report_status_to_api — we already know the post-action state without re-parsing psadmin (e.g. Running after start, Stopped after stop).
Proposed shape
- Add
config.ops.auto_report_status (bool, default false). One-time opt-in via psa config set auto_report_status true.
- When enabled and PSA-OPS is configured, lifecycle commands report the new state after a successful action.
--no-report escape hatch on each lifecycle command to suppress per-invocation.- Quiet when PSA-OPS isn't configured (existing
_report_status_to_api already handles it).
Out of scope
- Reporting failures / intermediate states (e.g.
Starting, Stopping).
- Auto-report on every command (read-only commands like
list and compare shouldn't push state).
Current state
Only
psa domain status --reportpushes status to PSA-OPS (via_report_status_to_apiatsrc/psa/commands/domain.py:171). Lifecycle commands (start,stop,restart,bounce,kill,configure,purge,flush) execute the action and exit without updating PSA-OPS. Users have to follow up withpsa domain status --reportto sync.Desired
After each lifecycle command's success, send the resulting status to PSA-OPS automatically. Reuse
_report_status_to_api— we already know the post-action state without re-parsingpsadmin(e.g.Runningafterstart,Stoppedafterstop).Proposed shape
config.ops.auto_report_status(bool, default false). One-time opt-in viapsa config set auto_report_status true.--no-reportescape hatch on each lifecycle command to suppress per-invocation._report_status_to_apialready handles it).Out of scope
Starting,Stopping).listandcompareshouldn't push state).