mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
kevinveenbirkenbachandClaude Opus 5
c55f508e05
The cosmos generator linked a consumer to its provider only through an '<role>' in group_names reference or an explicit provides: name. A hard dependency has neither -- pinning the provider on unconditionally is exactly what removes the Jinja reference the generator was reading -- so web-svc-asset's bond to web-svc-file vanished from the diagram the moment it became binding. Match a service key against the provider's own primary key from the registry, in both directions. Services the role turns off drew a solid 1:1 edge, claiming a mandatory relationship for something that carries nothing at deploy time. They now render as a red 0..0 edge; edge merging gained a real precedence so a provider consumed through two keys stays live when only one is off. Named colour, not hex: a '#' opens an entity code in the mermaid lexer and turns the whole diagram into a parse error on GitHub. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
50 lines
1.9 KiB
Markdown
50 lines
1.9 KiB
Markdown
# sys-service-terminator
|
|
|
|
## Description
|
|
|
|
Runs a collected list of systemd services at the **end of a play**.
|
|
This is useful for services where flush/restart is suppressed during setup,
|
|
but should be started once everything they depend on is ready.
|
|
|
|
## Overview
|
|
|
|
This role runs a collected list of systemd services at the end of a play.
|
|
|
|
## Cosmos
|
|
|
|
The diagram places sys-service-terminator in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).
|
|
|
|
```mermaid
|
|
flowchart LR
|
|
subgraph role [sys-service-terminator 💻]
|
|
svc_service_terminator["service-terminator"]
|
|
end
|
|
```
|
|
|
|
Solid `1:1` edges are fixed relationships; dashed `0..1` edges are conditional (enabled only in matching deployments); red `0..0` edges are turned off in this role. Node markers show the role's deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in `meta/main.yml`.
|
|
|
|
## Features
|
|
|
|
- **Automated provisioning:** Configured by Ansible without manual steps.
|
|
|
|
## How it works
|
|
|
|
- Consumes `system_service_run_list` (created by `sys-service` when `system_service_force_flush_final=true`).
|
|
- Enables and starts/restarts each service.
|
|
- Shows diagnostics (`systemctl status`, `journalctl -xeu`) on failure.
|
|
|
|
## Variables
|
|
|
|
- `system_service_run_list` (list): list of systemd unit names to run
|
|
- `SYS_SERVICE_RUNNER_STATE` (string): desired state (`started`, `restarted`, ...)
|
|
|
|
## Further Resources
|
|
|
|
- <https://www.freedesktop.org/software/systemd/man/systemctl.html>
|
|
|
|
## Credits
|
|
|
|
Implemented by **[Kevin Veen-Birkenbach](https://www.veen.world)**.
|
|
Part of the [Infinito.Nexus Project](https://s.infinito.nexus/code) and maintained by [Kevin Veen-Birkenbach](https://www.veen.world).
|
|
Licensed under the [Infinito.Nexus Community License (Non-Commercial)](https://s.infinito.nexus/license).
|