Remove ward docker exec #1206

New issue

Closed

opened 2026-07-13 22:21:45 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-13 22:21:45 +00:00

Member

Remove the ward-managed docker exec escape hatch.

Context:

ward dispatch is moving toward multi-node operation, where local Docker state cannot be treated as canonical control-plane state
ward docker exec is a direct local-Docker affordance gated by ward=true labels, which reinforces a host-local control model
the command is also not needed for the dispatch-state architecture and should leave the supported surface

Required changes:

remove the ward docker exec command registration and implementation
delete or rewrite tests that only exercise ward docker exec
remove docs/help references that advertise ward docker exec
keep any lower-level Docker helpers that are still needed internally by dispatch, launch, logs, drain, reap, or broker paths
do not remove internal docker exec/capture helpers unless they are unused after the public command is gone

Acceptance criteria:

ward docker exec no longer appears in help output
invoking ward docker exec fails as an unknown command, not as a label/permission error
tests cover the command surface removal or existing command-list tests are updated
pre-commit and the relevant Go test package pass

Related architecture issue: coilyco-flight-deck/ward#1205.

Remove the ward-managed docker exec escape hatch. Context: - ward dispatch is moving toward multi-node operation, where local Docker state cannot be treated as canonical control-plane state - ward docker exec is a direct local-Docker affordance gated by ward=true labels, which reinforces a host-local control model - the command is also not needed for the dispatch-state architecture and should leave the supported surface Required changes: - remove the ward docker exec command registration and implementation - delete or rewrite tests that only exercise ward docker exec - remove docs/help references that advertise ward docker exec - keep any lower-level Docker helpers that are still needed internally by dispatch, launch, logs, drain, reap, or broker paths - do not remove internal docker exec/capture helpers unless they are unused after the public command is gone Acceptance criteria: - ward docker exec no longer appears in help output - invoking ward docker exec fails as an unknown command, not as a label/permission error - tests cover the command surface removal or existing command-list tests are updated - pre-commit and the relevant Go test package pass Related architecture issue: coilyco-flight-deck/ward#1205.

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-13 22:31:42 +00:00

Remove ward docker exec #1208

coilyco-ops commented

2026-07-13 22:33:13 +00:00

Author

Member

WARD-OUTCOME: submitted

details

workflow: pull-request-and-merge; review summary: skipped because the temporary ward default pending brokered QA implementation felt straightforward after the command surface was traced, but the CLI fallback needed a fast-path guard to avoid the help-topic path confidence: high surprises: `urfave/cli` returned `No help topic for 'exec'` until the entrypoint rejected the path before dispatch follow-ups: watch PR #1208 until the director merges it

WARD-OUTCOME: submitted <details><summary>details</summary>workflow: pull-request-and-merge; review summary: skipped because the temporary ward default pending brokered QA implementation felt straightforward after the command surface was traced, but the CLI fallback needed a fast-path guard to avoid the help-topic path confidence: high surprises: `urfave/cli` returned `No help topic for 'exec'` until the entrypoint rejected the path before dispatch follow-ups: watch PR #1208 until the director merges it </details>