Iron-Legion/documentation
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

PRD: Clarify resolved questions in N8N orchestrator (auto-increment, PVE exclusion, LAN only)

Browse Source
This commit is contained in:
F.R.I.D.A.Y.
2026-06-05 21:59:34 -04:00
parent 2e15769409
commit c7df48b9a0
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
PRD Drafts/n8n-terraform-ansible-orchestrator.md
View File

@@ -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?** | # | Question | Decision |
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?** | 1 | Should `/build` auto-increment `vmid_base`? | **Yes** — default to auto-increment with optional explicit override |
4. **N8N webhook URL exposed via Tailscale or local LAN only?** | 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 ## 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 | | 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 | | 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 | | vmid_base tracking | Manual vs auto-increment | Auto-increment via PVE API query before apply |
| Fleet-update schedule | On-demand only vs weekly cron | On-demand only via `/fleet-update` | | Fleet-update schedule | On-demand vs cron | On-demand only via `/fleet-update` |