chore(ops-agent): re-sync max2 baseline — smoke_copilot_media_organizer #43

Merged
janpeter merged 1 commit from chore/ops-agent-baseline-copilot-smoke-max2 into master 2026-07-04 14:27:37 +02:00
Owner

Wat

Re-sync van de max2 ops-agent baseline naar de live /etc/ops-agent config. De drift-detector (ops-agent-host-config-discipline runbook) meldde 2 gedrifte files:

file hunks
deploy/max2-workflows/ops-agent/baseline/commands.yml 1
deploy/max2-workflows/ops-agent/baseline/flows/redeploy_media_organizer.yml 1

Review: was de live-wijziging bedoeld? — Ja

De live change is op 2026-06-19 14:14 toegepast (met .bak.20260619-141427 backups ernaast) en is coherent + functioneel:

  • nieuw commando smoke_copilot_media_organizer: docker exec media-organizer-webS4M_COPILOT_URL/health (read-only healthcheck, niet-destructief).
  • nieuwe flow-stap in redeploy_media_organizer met on_failure: continue (non-blocking).

Live geverifieerd: media-organizer-web draait en S4M_COPILOT_URL is gezet (http://100.118.195.120:8100), dus de smoke werkt echt.

Wat deze PR doet

Alleen de repo-baseline bijgewerkt zodat die byte-identiek is aan live — géén live-wijziging. Na merge leest de drift-detector de gemergede baseline en is de detector weer stil.

Conform §2 van de ops-agent-host-config-discipline runbook (double-edit; no self-merge — deze PR wacht op review).

## Wat Re-sync van de max2 ops-agent **baseline** naar de live `/etc/ops-agent` config. De drift-detector (`ops-agent-host-config-discipline` runbook) meldde 2 gedrifte files: | file | hunks | |---|---| | `deploy/max2-workflows/ops-agent/baseline/commands.yml` | 1 | | `deploy/max2-workflows/ops-agent/baseline/flows/redeploy_media_organizer.yml` | 1 | ## Review: was de live-wijziging bedoeld? — Ja De live change is op **2026-06-19 14:14** toegepast (met `.bak.20260619-141427` backups ernaast) en is coherent + functioneel: - **nieuw commando** `smoke_copilot_media_organizer`: `docker exec media-organizer-web` → `S4M_COPILOT_URL/health` (read-only healthcheck, niet-destructief). - **nieuwe flow-stap** in `redeploy_media_organizer` met `on_failure: continue` (non-blocking). Live geverifieerd: `media-organizer-web` draait en `S4M_COPILOT_URL` is gezet (`http://100.118.195.120:8100`), dus de smoke werkt echt. ## Wat deze PR doet Alleen de **repo-baseline** bijgewerkt zodat die byte-identiek is aan live — géén live-wijziging. Na merge leest de drift-detector de gemergede baseline en is de detector weer stil. Conform §2 van de `ops-agent-host-config-discipline` runbook (double-edit; **no self-merge** — deze PR wacht op review).
Live /etc/ops-agent had diverged from the version-controlled baseline
(drift-detector: commands.yml 1 hunk, flows/redeploy_media_organizer.yml 1 hunk).

The live change (applied 2026-06-19, .bak.20260619-141427 alongside) is
intentional and functional: a new smoke_copilot_media_organizer command
(docker exec media-organizer-web -> S4M_COPILOT_URL/health) plus a matching
on_failure:continue step in the redeploy_media_organizer flow. Verified live:
media-organizer-web is up and S4M_COPILOT_URL is set.

Re-syncing the repo baseline to match live per the ops-agent host-config
discipline runbook. No live change made; baseline now byte-identical to live.
janpeter merged commit 94e638ba7a into master 2026-07-04 14:27:37 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
janpeter/scrum4me-docker!43
No description provided.