make edge-plan / make edge: the Edge Stack through the Makefile #30

Closed
opened 2026-10-06 15:01:14 +00:00 by pit · 1 comment
Owner

Parent

#27

What to build

make edge-plan and make edge run the Edge Stack through the same gate as the Guest Target, sourcing the Edge's .env and passing the mandatory -var-file automatically, so the one required argument of that Stack cannot be forgotten and the plan cannot quietly propose destroys. The runbook's "the Makefile" section gains this Target's entry.

Acceptance criteria

  • make edge-plan and make edge source the Edge's .env and pass the -var-file without the caller supplying either.
  • The apply gate is identical to the Guest Target's: the plan artifact is rendered, the environment word is typed, and the reviewed artifact is applied.
  • make edge against an unchanged estate reports no changes and mutates nothing.
  • The runbook documents this Target.

Blocked by

  • ##29 — the Makefile scaffold and its apply gate.
## Parent #27 ## What to build `make edge-plan` and `make edge` run the Edge Stack through the same gate as the Guest Target, sourcing the Edge's `.env` and passing the mandatory `-var-file` automatically, so the one required argument of that Stack cannot be forgotten and the plan cannot quietly propose destroys. The runbook's "the Makefile" section gains this Target's entry. ## Acceptance criteria - [ ] `make edge-plan` and `make edge` source the Edge's `.env` and pass the `-var-file` without the caller supplying either. - [ ] The apply gate is identical to the Guest Target's: the plan artifact is rendered, the environment word is typed, and the reviewed artifact is applied. - [ ] `make edge` against an unchanged estate reports no changes and mutates nothing. - [ ] The runbook documents this Target. ## Blocked by - ##29 — the Makefile scaffold and its apply gate.
Author
Owner

Implemented and merged in #39 (merge ef029c5). Refs #30 was not a closing keyword, so the merge did not auto-close this.

Implemented and merged in #39 (merge ef029c5). Refs #30 was not a closing keyword, so the merge did not auto-close this.
pit closed this issue 2026-10-06 15:50:23 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
olympus/infra-forge#30
No description provided.