Add temporary maintenance for automatic rule actions - #41
Merged
Merged
Conversation
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.
Allow operators to pause automatic remediation during container maintenance while collection, audit and manual controls continue. Store a finite per-container deadline in the existing atomic, locked state file; preserve restart budgets and cooldowns. Resume at expiry or on explicit cancellation.
Includes offline CLI (0–86400 seconds), opt-in authenticated UI controls (15 min, 1 hour, resume), status/Prometheus indicators, and audited activation/skips/expiry. Existing protected containers stay protected. Docker restart policies, other agents and external notifications are unaffected. State schemas 1–3 migrate to 4 on use; older binaries reject schema 4. Maintenance transitions conservatively reset shared sustained-condition observations, as documented.
Validation: 279 Python tests collected (13 Docker tests delegated to CI), 9 focused maintenance tests; strict Sphinx build; desktop/mobile browser tests including maintenance confirmation and overflow. Public demo maintenance controls remain disabled; no release/version bump in this PR.