Add Dynu Terraform brownfield DNS documentation layer
This commit is contained in:
@@ -10,17 +10,21 @@ It does **not** replace Docker Compose as runtime deployment authority.
|
||||
- Physical host metadata represented in Terraform locals/outputs.
|
||||
- Select Docker container mirror resources for documentation-oriented tracking.
|
||||
- Outputs that can support documentation and later downstream tooling.
|
||||
- Dynu DNS domain/record import and documentation inventory.
|
||||
|
||||
## What Terraform is not used for (today)
|
||||
|
||||
- Replacing `services-up.sh` / Compose for day-to-day app runtime orchestration.
|
||||
- Broad, immediate greenfield provisioning of the whole stack.
|
||||
- Casual `apply` operations across all infrastructure.
|
||||
- Replacing Dynu as DNS authority.
|
||||
- Blindly recreating production DNS records without import/reconciliation.
|
||||
|
||||
## Directory map
|
||||
|
||||
- `proxmox/` — imported/reconciled VM resources and host metadata outputs.
|
||||
- `docker/` — selective Docker container import/mirror resources.
|
||||
- `dynu/` — Dynu DNS brownfield import/reconciliation and DNS documentation outputs.
|
||||
- `bootstrap/` — backend/provider bootstrap scaffolding.
|
||||
- `modules/` — placeholder module directories for future stable abstractions.
|
||||
- `scripts/reconcile_from_plan.sh` — helper to convert generated plan config into reviewable draft files.
|
||||
|
||||
Reference in New Issue
Block a user