ADR: Prod and PRE share one Stack split by target #36

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

Parent

#27

What to build

An ADR recording why Prod and PRE share one Stack and one OpenTofu state, split by Target selection, rather than being two separate Stacks — the trade-off against splitting into two states, and against workspaces. The record is written with the next free number in the ADR sequence at the time of writing, not a reserved number, so an ADR merged first does not collide.

Acceptance criteria

  • The ADR is written with the next available number at write time, and a row is added to the ADR index.
  • It records the trade-off against splitting into two Stacks and against workspaces.
  • No earlier ADR file is renumbered or rewritten.

Blocked by

  • ##34 — make prod composes the stack end to end.
  • ##35 — make pre and make pre-down.
## Parent #27 ## What to build An ADR recording why Prod and PRE share one Stack and one OpenTofu state, split by Target selection, rather than being two separate Stacks — the trade-off against splitting into two states, and against workspaces. The record is written with the next free number in the ADR sequence at the time of writing, not a reserved number, so an ADR merged first does not collide. ## Acceptance criteria - [ ] The ADR is written with the next available number at write time, and a row is added to the ADR index. - [ ] It records the trade-off against splitting into two Stacks and against workspaces. - [ ] No earlier ADR file is renumbered or rewritten. ## Blocked by - ##34 — `make prod` composes the stack end to end. - ##35 — `make pre` and `make pre-down`.
pit closed this issue 2026-10-06 20:30:46 +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#36
No description provided.