mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 04:06:42 +00:00
kevinveenbirkenbachandClaude Opus 5
7bc12e55f3
aceb5295efmoved Cosmos, Quick Setup and Credits out of the committed role READMEs and into the documentation build's own scratch checkout, so a committed copy can no longer go stale when the metadata moves. Merging feature/designer (ebad39422c) took origin/main's side of those files, which still carries them, and reinstated all 290 along with the cosmos make target and its i8cos alias. tests/lint/ansible/roles/test_readme.py hard-fails on a committed copy, and the reinstated Credits block credited one person with two URLs, which tripped the credits-attribution lint as well. Stripped with the repository's own fence-aware parser against MANAGED_SECTIONS, not with a line filter: the Cosmos block holds a mermaid fence a naive filter would cut through. The result is byte-identical toaceb5295effor every README that carries no prose change since. The cosmos target wrote the forbidden section straight back into the checkout, so it goes with them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
System Maintenance Lock
Description
This role provides a locking mechanism to ensure that critical services are not interrupted during maintenance activities such as updates, backups, or patch applications. It waits for specified services to stop and prevents conflicting operations.
Overview
The role performs the following:
- Blocks execution until specified services have stopped.
- Implements retry logic with a configurable timeout.
- Ensures that maintenance tasks are executed only when the system is in a safe state.
Purpose
The primary purpose of this role is to safeguard system stability during maintenance by preventing conflicts with running services. It ensures that maintenance operations proceed only when the environment is ready.
Features
- Service Locking: Blocks maintenance tasks until critical services are stopped.
- Timeout and Retry Logic: Configurable wait times and maximum attempts.
- Conflict Avoidance: Prevents interference between maintenance operations and running services.