Skip to content

Proposal — self-updating runbook wiki

In one line

Turn our four Ansible projects' provisioning, decommission and P1 runbooks into an always-current internal wiki — for the price of a team lunch — using the Azure DevOps, self-hosted n8n and Azure OpenAI we already own.

  •   Executive summary

    Pros, cons and risks on one page.

    Summary

  •   Cost

    ~$30–50/mo, zero new infrastructure.

    Cost model

  •   Security

    Private, identity-first, PR-gated.

    Security

  •   Risks & fixes

    Every "what could go wrong" with the fix.

    Risks

  •   Roadmap

    Value in weeks, not quarters.

    Roadmap

At a glance

Metric Value
Ansible projects in scope 4
Changes PR-gated (human review) 100%
New monthly cost ~$30–50 (tokens only)
New infrastructure $0
Time to live demo 1–2 weeks
Regions EMEA · Brazil · China · on-prem

Built entirely on assets we already own: Azure DevOps, self-hosted n8n, and Azure OpenAI.

Architecture

flowchart TB
  subgraph SRC[Sources]
    R1[4 Ansible repos - Azure DevOps]
    R2[SharePoint - docs, Excel, legacy]
    R3[Power BI + SNOW reports]
    R4[Teams + Outlook comms - confidential]
  end
  SRC -->|webhooks / delta / hooks| N8N[n8n - self-hosted, existing]
  N8N --> CLS{Classify}
  CLS -->|normal| DRAFT[AI Drafter - Azure OpenAI]
  CLS -->|deleted| TOMB[Tombstone - no LLM]
  CLS -->|confidential| LINK[Link-only stub - no LLM, no mirror]
  DRAFT --> PR[Azure DevOps PR - owner review]
  TOMB --> PR
  LINK --> PR
  PR -->|human review| MERGE{Merge}
  MERGE --> WIKI[Code Wiki - Git-backed]
  WIKI -.Phase 2.-> RAG[Ask-the-runbooks - ACL-trimmed]