briefings: mongodb-cluster still advertised the removed physical backup mode - #522
Merged
Conversation
…up mode My error, and a good illustration of the drift the briefing rule exists to catch. While removing physical mode I edited the briefing from inside the worktree using a `../../briefings/` path -- which resolves to the MAIN worktree, not the branch. So the correction never reached the PR, and #521 merged with the briefing still describing PBM physical backups as an available option, a `-physical-backup` workload that no longer renders, and a trap warning that the physical restore is "unverified and may be architecturally blocked". It is not unverified any more: it was measured, it cannot work, and the mode is gone. The trap now states the actual cause -- the pbm-agent image has no mongod -- and notes that the earlier hypothesis about the platform restarting mongod as PID 1 was wrong. Documentation only; `helm template` output is byte-identical, so this is fixed in place per the in-place rule rather than as a new version. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation only —
helm templateoutput is byte-identical, so this is an in-place fix rather than a new version.My error. While removing
backup.mode: physicalI edited the briefing from inside the worktree using a../../briefings/path, which resolves to the main worktree rather than the branch. The correction never reached the PR, so #521 merged with the briefing still:{release}-mongo-physical-backupworkload that no longer rendersIt is not unverified any more. It was measured and it cannot work: PBM's physical restore must execute
mongod, and thepbm-agentimage does not contain it —check mongod binary: run: exec: \"mongod\": executable file not found in \$PATH. The trap now states that, and notes the earlier hypothesis (the platform restarting mongod as PID 1) was wrong.A briefing that goes stale is worse than none, since it is consulted precisely when someone is already confused — and this one would have told a reader to reach for a mode that no longer exists.
🤖 Generated with Claude Code