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>
2.0 KiB
User
Description
This role configures a basic user environment (shell dotfiles and SSH authorized_keys)
for a user selected via user_key.
Overview
This role executes common tasks for user environment configuration.
Cosmos
The diagram places User 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 [user 💻]
svc_user["user"]
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.
User data resolution
User data is resolved via lookup('users', user_key) and referenced via user_key.
Callers may pass user_config to override the resolved lookup result for one invocation.
Resolution rules:
user_usernameis resolved fromlookup('users', user_key).username(fallback:user_key)- Home path and ownership are based on
user_username - SSH keys are read from
lookup('users', user_key).authorized_keys
Required input
user_key
Optional user fields
lookup('users', user_key).username(defaults touser_key)lookup('users', user_key).authorized_keys(list; may be empty)- optional include-role var
user_configto override the lookup result for the current call
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).