chore(ops-agent): resync drift baseline na copilot+digiplein deploys #84
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/ops-agent-baseline-resync-copilot-digiplein"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Re-sync van de version-controlled ops-agent drift-baseline naar de live
/etc/ops-agentop 154.De daily drift-detector (
ops-agent-drift.timer) pingde mac:jp op 2026-06-12 met 3 geflagde files. De drift komt volledig uit twee bewuste deploys (copilot-rollout + DigiPlein-deploy); de baseline liep er gewoon op achter.Wijzigingen in
deploy/ops-agent/baseline/commands.yml:scrum4me-copilot+digipleinin de build/recreate-allowlist; nieuwe cmdsdigiplein_git_reset_main+digiplein_migrateflows/update_copilot.yml(nieuw)flows/update_digiplein.yml(nieuw)flows/update_ops_dashboard.yml(git_submodule_update-stap; liep achter)Na merge is de repo-baseline weer gelijk aan live. De runtime-baseline op
/srv/scrum4me/ops-agent-drift/baseline/wordt los gesynct (handmatige apply-stap per runbook).🤖 Generated with Claude Code