# 2026-07-07 — Mineralogical Record: Add Tucson site to GuruRMM

## User
- **Executed by:** ClaudeTools Discord Bot (GURU-BEAST-ROG)
- **Requested by:** Mike Swanson (@azcomputerguru, via Discord) - admin
- **Role:** automation (acting on the requester's behalf)

## Session Summary
Mike requested (via Discord, #tech-department thread 1524160229665804349): "Add Minerological Record to RMM, sites Main and Tucson."

Before creating anything, checked the vault and GuruRMM API for an existing client. Found that the client already existed: "Mineralogical Record" (correct spelling — Mike's request had "Minerological") was created in GuruRMM on 2026-07-03 with client_id fad460a5-aba9-4314-ac62-56f2412cc8d3 and one site, Main (BLUE-MOON-8542), whose enrollment key was already vaulted at clients/mineralogical-record/gururmm-site-main.sops.yaml.

Only the Tucson site was missing. Created it via POST /api/sites, captured the one-time api_key from the create response, wrote it to a new SOPS vault entry, encrypted in place, verified round-trip decryption, and committed/pushed the vault repo (required a pull --rebase first due to a remote update). Posted the mandatory [RMM] write alert to #dev-alerts.

## Key Decisions
- Did NOT create a duplicate client. Vault search for "mineral" surfaced the existing entry before any write; confirmed live via GET /api/clients.
- Used the canonical spelling "Mineralogical Record" (matching the existing RMM client and vault slug `mineralogical-record`) rather than Mike's "Minerological".
- Followed the /rmm onboard vault pattern for the new site key: secrets under `credentials:` block, quoted date, sops --encrypt --in-place with --config pointing at the vault's .sops.yaml, ENC[ grep verification, round-trip read via vault.sh.
- Wrote the one-time site create response to a repo-relative scratch file (./.site-tucson.json, deleted after vaulting) — never /tmp, per Windows path-mismatch rule.

## Problems Encountered
- Vault repo push rejected (remote had new commits). Resolved with `git pull --rebase` then push — clean fast-forward, no conflicts.

## Configuration Changes
- GuruRMM: new site "Tucson" under client Mineralogical Record (no client changes; Main site untouched).
- Vault (separate repo, pushed): created `clients/mineralogical-record/gururmm-site-tucson.sops.yaml` — commit "add: Mineralogical Record GuruRMM site Tucson enrollment key (EAST-VALLEY-4358)".
- ClaudeTools repo: this session log only.

## Credentials & Secrets
- Tucson site agent enrollment api_key (grmm_...) — vaulted at `clients/mineralogical-record/gururmm-site-tucson.sops.yaml` under credentials.api_key. One-time value from the site create response; regenerable via POST /api/sites/d7e02969-71f0-4bc3-8f7d-eda20c3b84a4/regenerate-key if lost.
- Main site key (pre-existing): `clients/mineralogical-record/gururmm-site-main.sops.yaml`.
- Vault paths read: `infrastructure/gururmm-server.sops.yaml` (RMM API auth, via rmm-auth.sh).

## Infrastructure & Servers
- GuruRMM API: http://172.16.3.30:3001
- Client: Mineralogical Record — client_id fad460a5-aba9-4314-ac62-56f2412cc8d3
- Site Main: site_id e36fcea4-1e47-4ec9-b706-fea869faa8a0, site_code BLUE-MOON-8542 (created 2026-07-03)
- Site Tucson: site_id d7e02969-71f0-4bc3-8f7d-eda20c3b84a4, site_code EAST-VALLEY-4358 (created this session)
- Install pages: https://rmm.azcomputerguru.com/install/BLUE-MOON-8542 , https://rmm.azcomputerguru.com/install/EAST-VALLEY-4358
- Tucson MSI: https://rmm.azcomputerguru.com/api/sites/d7e02969-71f0-4bc3-8f7d-eda20c3b84a4/installer

## Commands & Outputs
- `vault.sh search "mineral"` → found existing clients/mineralogical-record/gururmm-site-main.sops.yaml
- `GET /api/clients` → existing client, site_count=1
- `POST /api/sites {"client_id":"fad460a5-...","name":"Tucson"}` → site created, EAST-VALLEY-4358
- `sops --config "$VR/.sops.yaml" --encrypt --in-place` → 8 ENC[ markers, round-trip verified
- `post-bot-alert.sh "[RMM] Mike added site 'Tucson' (EAST-VALLEY-4358) ..."` → posted to #dev-alerts (message_id=1524160762204000278)

## Pending / Incomplete Tasks
- Agents not yet installed at either site — use the install pages / MSI URLs above when deploying.
- Syncro ticket: offered to Mike; awaiting his answer in the Discord thread.
- Run `/rmm diagnose <hostname> mineralogical-record` after first agents enroll (onboarding baseline).

## Reference Information
- Discord thread: 1524160229665804349 (#tech-department)
- #dev-alerts message: 1524160762204000278
- Vault commit: "add: Mineralogical Record GuruRMM site Tucson enrollment key (EAST-VALLEY-4358)"
- Wiki article exists: wiki/clients/mineralogical-record.md
