coilyco-flight-deck/ward

Watch

ward should not mention AWS anywhere #1478

New issue

Closed

opened 2026-07-18 03:13:01 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-18 03:13:01 +00:00

Owner

Ward has no business knows about any cloud platforms except for a forge and an issue tracker. Users are responsible for figuring out creds (which is what my AWS is for)

coilyco-ops added the

autonomy

headless

priority

labels

2026-07-28 08:47:27 +00:00

coilyco-ops referenced this issue

2026-07-28 08:52:04 +00:00

Bound logs reads for fresh container-starting engineers with no transcript yet #1594

coilyco-ops referenced this issue from a commit

2026-07-28 09:16:11 +00:00

Remove cloud credential handling

coilyco-ops closed this issue

2026-07-28 09:16:11 +00:00

coilyco-ops commented

2026-07-28 09:19:42 +00:00

Member

WARD-WORKFLOW: done ✅

details

workflow: merge-remote-main; review summary: skipped - the in-container review gate was intentionally skipped because the temporary ward default is pending brokered QA.

Implemented: removed Ward's built-in cloud credential export/mount path, made Forgejo credential resolution explicit env-or-broker, kept director reach to tailnet only, and cleaned docs/tests/source text so the repo no longer contains those provider references.

Validation: ward exec test, ward exec build, ward exec vet, ward exec lint, pre-commit, and final reference sweeps passed. Merged to main and pushed 29c19a7e.

Post-push: direct Forgejo API check showed gate-and-promote success and the release job success for 29c19a7e; promote-draft-assets failed in the release workflow, matching nearby runs.

Felt: broad but mostly mechanical once the credential boundary was clear.

Confidence: high.

Surprises: the full test suite initially exposed a transient tempdir cleanup race and filled cache space; reruns passed after clearing stale cache.

Follow-ups: investigate the recurring promote-draft-assets release job failure separately.

WARD-WORKFLOW: done ✅ <details><summary>details</summary> workflow: merge-remote-main; review summary: skipped - the in-container review gate was intentionally skipped because the temporary ward default is pending brokered QA. Implemented: removed Ward's built-in cloud credential export/mount path, made Forgejo credential resolution explicit env-or-broker, kept director reach to tailnet only, and cleaned docs/tests/source text so the repo no longer contains those provider references. Validation: `ward exec test`, `ward exec build`, `ward exec vet`, `ward exec lint`, pre-commit, and final reference sweeps passed. Merged to `main` and pushed `29c19a7e`. Post-push: direct Forgejo API check showed `gate-and-promote` success and the release job success for `29c19a7e`; `promote-draft-assets` failed in the release workflow, matching nearby runs. Felt: broad but mostly mechanical once the credential boundary was clear. Confidence: high. Surprises: the full test suite initially exposed a transient tempdir cleanup race and filled cache space; reruns passed after clearing stale cache. Follow-ups: investigate the recurring `promote-draft-assets` release job failure separately. </details>

coilyco-ops commented

2026-07-28 09:19:49 +00:00

Member

WARD-WORKFLOW: reservation-released

release details

Run finished with WARD-WORKFLOW: done ✅.

ward container reap released container engineer-codex-ward-1478 (--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs --override-reservation.

— Codex, via ward agent

WARD-WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARD-WORKFLOW: done ✅`. `ward container reap` released container `engineer-codex-ward-1478` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue

2026-07-28 09:20:04 +00:00

Inspect failed release run 2495 after AWS reference removal landed #1597

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/ward#1478

No description provided.

Rows
Columns