Repository navigation
Pause and resume the retained Email recovery reader safely #6048
Description
🤖 Generated by the Agentic Engineer
The retained Email recovery reader needs a reversible pause so infrastructure maintenance can continue while its recovery data remains available. The existing disposal operation correctly remains unavailable; it must keep its current backup-validity requirements.
Acceptance criteria
- Provide separate, explicitly confirmed pause and resume operations in reviewed, protected, main-only workflows using the deployment lock and existing credential custody.
- Bind the fixed diagnostic copy to independent resource witnesses. Refuse changed, foreign, ambiguous or incomplete state before any write.
- Pause with normal, bounded, UID-fenced reader termination. Preserve its namespace, storage claim, volume, backend, replicas, authentication, encryption key and configuration. Never force deletion or detach storage directly.
- Confirm actual reader absence and volume detachment before reporting maintenance clearance. Unknown or incomplete outcomes remain unverified.
- Resume only the same retained copy with the reviewed reader definition and unchanged recovery inputs. Verify the replacement reader and durably rebind its new identity for later authorized observations.
- Cover successful pause/resume and changed identities, missing recovery material, unsafe attachments, uncertain deletion and replacement-reader cases. Complete required validation, current-head review, protected delivery and live readback.
- Preserve the existing expired-backup disposal gate, source mailbox and all other recovery copies. Keep private identifiers and content out of public output.
Part of #5578. This is a repair needed to finish the already-started Email recovery and storage-maintenance work. Candidate-image adoption waits behind recovery release; no extra scratch allocation is authorized by this operation.
Reacted by coderabbitai
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
None yet
Start date
None yet
Target date
None yet
Effort
None yet
Projects
- Status
Activity
coderabbitai commentedon Nov 11, 2026
🔗 Related PRs
#5839 - fix(email): verify and dispose the retained recovery copy [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
chore: agent-claim #6048 nonce=85c4dc60ab4926e91c1ac8fe75f18843
chore: agent-claim #6048 nonce=f542c774cc5e0e19ee2f1b29b8d89808
devantler commentedon Nov 11, 2026
This repair is being implemented to unblock the Email recovery and storage-maintenance work already in progress. No new Ready work was pulled. The original recovery work keeps its existing start and retention requirements.
Draft #6074 records the first input-validation step. Durable custody, the protected pause/resume operations and live verification remain unfinished; this is not permission to stop a reader or release storage. The existing disposal protections remain unchanged.
First implementation started: 2026-11-11. The recovery issue remains open until the actual pause, detachment and restart are verified.
feat(email): prepare retained reader inputs in protected custody
fix(email): preserve runner masking during custody preparation
feat(email): retain the fixed recovery volume before maintenance
fix(email): avoid shadowing a built-in in recovery snapshots