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>
Development Utilities
Description
Visual Studio Code is a powerful source code editor with a wide plugin ecosystem, supporting development workflows across many languages and platforms. See also the Arch Wiki - Development Tools and general Software Engineering on Wikipedia.
Overview
This role builds upon core workstation and package management components to deliver a clean, editor-ready base for developers. It installs core tools and editors necessary to begin building, editing, and managing source code projects.
Cosmos
The diagram places Development Utilities 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 [dev-core 💻]
svc_core["core"]
end
subgraph dependents [Dependents]
dpt_dev_arduino["dev-arduino 💻 ⚙️"]
dpt_dev_python["dev-python 💻 ⚙️"]
end
svc_core -- "1:1" --> dpt_dev_arduino
svc_core -- "1:1" --> dpt_dev_python
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
To reduce setup time and ensure consistency across developer workstations, this role prepares a functional and extensible foundation for software engineering work.
Features
- Installs Visual Studio Code: A powerful code editor with a wide plugin ecosystem.
- Extensible Design: Acts as a base layer for more specific development stacks (e.g., web, Python, embedded).
- Persona Integration: Serves as a reusable foundation for developer-focused workstation bundles.
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).