From c7df48b9a08e3780a180be8138e688459fe17264 Mon Sep 17 00:00:00 2001 From: "F.R.I.D.A.Y." Date: Fri, 5 Jun 2026 21:59:34 -0400 Subject: [PATCH] PRD: Clarify resolved questions in N8N orchestrator (auto-increment, PVE exclusion, LAN only) --- .../n8n-terraform-ansible-orchestrator.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/PRD Drafts/n8n-terraform-ansible-orchestrator.md b/PRD Drafts/n8n-terraform-ansible-orchestrator.md index 4c2d83a..dd4aa0d 100644 --- a/PRD Drafts/n8n-terraform-ansible-orchestrator.md +++ b/PRD Drafts/n8n-terraform-ansible-orchestrator.md @@ -148,14 +148,14 @@ Artemis parses → action=fleet_update --- -## 7. Open Questions +## 7. Resolved Questions -1. **Should `/build` auto-increment `vmid_base` from last used, or always require explicit input?** -2. **Should N8N trigger a Gitea commit of generated inventory after apply?** -3. **Should `/fleet-update` include PVE nodes via `apt` (not `dist-upgrade`) differently?** -4. **N8N webhook URL exposed via Tailscale or local LAN only?** - ---- +| # | Question | Decision | +|---|----------|----------| +| 1 | Should `/build` auto-increment `vmid_base`? | **Yes** — default to auto-increment with optional explicit override | +| 2 | Should N8N trigger Gitea commit of generated inventory? | **No** — LXCs are ephemeral, inventory is temporary | +| 3 | Should `/fleet-update` include PVE nodes? | **No** — PVE self-managed, separate workflow later | +| 4 | N8N webhook via Tailscale or LAN? | **LAN IP only** — `192.168.15.182`, no prod server access | ## 8. Decision Points @@ -163,5 +163,5 @@ Artemis parses → action=fleet_update |----------|---------|-------------| | N8N SSH key | `artemis_key` vs dedicated `n8n_key` | `artemis_key` for POC; rotate to dedicated key later | | Notification target | Telegram vs Discord vs both | Both via existing gateway webhook | -| vmid_base tracking | Manual vs auto-increment vs check-before-apply | Manual for POC; auto-track in Phase 4 | -| Fleet-update schedule | On-demand only vs weekly cron | On-demand only via `/fleet-update` | +| vmid_base tracking | Manual vs auto-increment | Auto-increment via PVE API query before apply | +| Fleet-update schedule | On-demand vs cron | On-demand only via `/fleet-update` |