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>
52 lines
2.2 KiB
Markdown
52 lines
2.2 KiB
Markdown
# sys-pip-install
|
|
|
|
## Description
|
|
|
|
This role installs or upgrades a Python package **system-wide** using the system `pip` (`python3 -m pip`).
|
|
It is intended for CLI tools that should be available globally (e.g., maintenance utilities).
|
|
|
|
> This role depends on `sys-pip`, which ensures that `pip` is installed on the target system.
|
|
|
|
## Overview
|
|
|
|
- Ensures the system `pip` is available (via `sys-pip`).
|
|
- Installs or upgrades a package specified by `package_name`.
|
|
- Designed for non-interactive automation (CI/maintenance hosts).
|
|
|
|
## Cosmos
|
|
|
|
The diagram places sys-pip-install 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-pip-install 💻]
|
|
svc_pip_install["pip-install"]
|
|
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.
|
|
|
|
## Variables
|
|
|
|
### Required
|
|
|
|
- `package_name` (string)
|
|
Name of the Python package to install (e.g., `dockreap`, `backup-docker-to-local`).
|
|
|
|
## Notes / Caveats
|
|
|
|
- The role checks whether `pip` from `ansible_python_interpreter` supports `--break-system-packages` and only uses it (plus `PIP_BREAK_SYSTEM_PACKAGES=1`) when available.
|
|
This keeps the role compatible with older `pip` versions (e.g., some CentOS/RHEL systems).
|
|
- Use with care: installing Python packages system-wide can conflict with OS package management.
|
|
For isolated installs of CLI tools, consider `pipx` instead.
|
|
|
|
## 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).
|