Files
computer-playbook/roles/user-workstation
kevinveenbirkenbachandClaude Opus 5 7bc12e55f3 fix(docs): drop the generated sections the designer merge put back
aceb5295ef moved Cosmos, Quick Setup and Credits out of the committed role
READMEs and into the documentation build's own scratch checkout, so a
committed copy can no longer go stale when the metadata moves. Merging
feature/designer (ebad39422c) took origin/main's side of those files, which
still carries them, and reinstated all 290 along with the cosmos make target
and its i8cos alias. tests/lint/ansible/roles/test_readme.py hard-fails on a
committed copy, and the reinstated Credits block credited one person with two
URLs, which tripped the credits-attribution lint as well.

Stripped with the repository's own fence-aware parser against
MANAGED_SECTIONS, not with a line filter: the Cosmos block holds a mermaid
fence a naive filter would cut through. The result is byte-identical to
aceb5295ef for every README that carries no prose change since.

The cosmos target wrote the forbidden section straight back into the
checkout, so it goes with them.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-10-06 01:50:43 +02:00
..
…
…

Workstation User

Description

This role creates the workstation user defined by WORKSTATION_USER and configures its basic environment. It integrates with the shared user role to deploy shell dotfiles and SSH authorized_keys.

Overview

This role creates the workstation user selected via WORKSTATION_USER and configures the user environment.

Features

  • Automated provisioning: Configured by Ansible without manual steps.

User data resolution

User data must be defined under users.<name> and selected via WORKSTATION_USER.

Minimum required fields:

  • WORKSTATION_USER
  • users.<WORKSTATION_USER>.username (defaults to WORKSTATION_USER if missing)

Optional fields:

  • users.<WORKSTATION_USER>.uid
  • users.<WORKSTATION_USER>.gid
  • users.<WORKSTATION_USER>.shell
  • users.<WORKSTATION_USER>.groups (list)
  • users.<WORKSTATION_USER>.authorized_keys (list; may be empty)

Notes

  • Sudo can be enabled via user_workstation_enable_sudo.
  • Password handling is intentionally conservative. If you want a password, set users.<WORKSTATION_USER>.password (plain) and enable user_workstation_set_password.