mrcharles
19b2891102
Questions-file answers retired into docs/adr per the Redmine-first model. https://projects.knownelement.com/issues/705
896 B
ADR 0001: GLPI change logging from CLI, starting now
Status: accepted (2026-09-04, founder ruling OQ7). Discourse index: https://community.turnsys.com/t/297 — repo topic: https://community.turnsys.com/t/319 Ticket: https://projects.knownelement.com/issues/705
Context
Prod work needs approved Change Requests in GLPI (the CMDB), but waiting for the full GLPI/Redmine integration polish would leave prod changes untracked in the meantime.
Decision
Start logging production changes to GLPI NOW via scripts/glpi-change.sh
(CLI over the GLPI REST API). Note: the newer mglpi connector had a
change-create regression (#797) — glpi-change.sh remains the working path.
Consequences
Every prod-target op can carry a CR id (enforced by repo CHANGE GATEs like
PFVCluster's .crush/active-cr). CMDB rulings C1-C3 (itemtype, agent write
access, refresh cadence) are ticketed as #801.