Files
computer-playbook/roles/pkgmgr-install/README.md
kevinveenbirkenbachandClaude Opus 5 c55f508e05 feat(readme): draw mandatory and disabled service relations
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>
2026-08-17 18:02:31 +02:00

2.6 KiB

Package Manager Installation

Description

This Ansible role installs Kevin's Package Manager and updates packages using pkgmgr on Arch Linux systems. It provides a unified interface for package installation and update management, ensuring consistent deployment across environments.

Overview

The role abstracts package management operations using pkgmgr. It ensures the package manager itself is updated once per run and provides idempotent installation and update routines for specified packages.

Cosmos

The diagram places Package Manager Installation 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).

flowchart LR
    subgraph role [pkgmgr-install 💻]
        svc_pkgmgr_install["pkgmgr-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.

Purpose

The purpose of this role is to automate the installation and update process for Infinito.Nexus-related applications or other managed packages using pkgmgr. It simplifies package handling and enforces best practices for package deployment in automated environments.

Features

  • Automatic pkgmgr Update: Ensures the package manager is always up-to-date.
  • Idempotent Package Installation: Only installs packages when necessary.
  • Flexible Notification: Supports handler notification for post-install actions (e.g., Docker Compose builds).
  • Optional Privilege Escalation: Controlled via the pkgmgr_become variable (default: true).

Role Variables

Name Description Default
package_name Name of the package to install/update (required)
package_notify Handler to notify on package installation/update ""

Credits

Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).