kevinveenbirkenbachandClaude Opus 5
cd5b59d0a1
53c120aaac paired "become: false" with "become_user" on the desktop roles.
Setting become to false means do not escalate, so the sibling become_user is
inert and the task runs as the connection user: pipx installed the Blender MCP
server into /root and the editor extension landed in the profile of root. The
package install inside the addon file now pins become_user to root explicitly,
because it would otherwise inherit the workstation user from the apply block of
the include and run apt unprivileged.
Two consequences of the same chain ship with it, because no half of it leaves a
deployable state on its own:
- The registration inferred an installed editor from services.code.enabled, but
dsk-code declares nothing for code-oss, vscode or vscodium on Debian and
RedHat, so no editor can exist there and the command exited 2. It now probes
the binary and registers only when it resolves.
- The CLI test resolved the server through PATH and read the config under HOME
while running as root. It now uses absolute paths rendered from the role vars
and reads the registry claude writes as a file, the way the test of
dsk-gnt-claude already does.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>Code
Description
Visual Studio Code in a selectable flavor: the distribution's Code - OSS build, VSCodium, or Microsoft's own binary.
Overview
services.code.flavor picks one of code-oss, vscodium or vscode. The three builds conflict at package level, so the role removes the other two before installing the chosen one.
The role also carries the editor extensions of the agents the same host deploys: when dsk-gnt-claude is in the host's groups, the Claude Code extension is installed into the chosen flavor. Code - OSS and VSCodium resolve extensions through Open VSX, which carries that extension as well.
dsk-gnt-cursor and dsk-gnt-pi carry no entry in that map. Cursor is a full editor rather than an extension, and neither vendor publishes an extension on Open VSX, so there is nothing to install into Code for them. Both agents are used from their own binary.
Features
- Flavor selectable: one setting switches between Code - OSS, VSCodium and the Microsoft build.
- Conflict-free switch: the other flavors are removed first, because they claim the same binary.
- Agent-aware: an agent role on the same host brings its editor extension along.
- Refused early: an unknown flavor aborts the deploy with the list of carried flavors.