system/roles
Marty Oehme 5dd160727a
fix(roles): Default to root as user name
Always default to 'root' as a user_name if no variable has been set.
This can easily happen as not every role sets the variable and instead
we only set it once in the user role. 

Another way to possibly go about it in the future would be to inject the
'user_name' into each role that needs it as one of that role's default
variables. If it is specified by the user somewhere it _should_
override those defaults, though I have to read up on the exact variable
precedence.
2025-03-16 17:44:19 +01:00
..
acpi feat(acpi): Add custom LID event handling 2025-03-13 11:24:17 +01:00
backup ref(roles): All roles use desired package state 2025-03-13 11:24:14 +01:00
base fix(roles): Default to root as user name 2025-03-16 17:44:19 +01:00
bluetooth/tasks ref(roles): All roles use desired package state 2025-03-13 11:24:14 +01:00
display_manager feat(pipewire): Add alsa integration 2025-03-13 11:24:16 +01:00
fonts ref(roles): All roles use desired package state 2025-03-13 11:24:14 +01:00
gnupg/tasks fix(roles): Default to root as user name 2025-03-16 17:44:19 +01:00
host ref(roles): All roles use desired package state 2025-03-13 11:24:14 +01:00
keyd ref(roles): All roles use desired package state 2025-03-13 11:24:14 +01:00
network ref(roles): All roles use desired package state 2025-03-13 11:24:14 +01:00
packages/tasks ref(roles): All roles use desired package state 2025-03-13 11:24:14 +01:00
pipewire fix(roles): Default to root as user name 2025-03-16 17:44:19 +01:00
power fix(roles): Default to root as user name 2025-03-16 17:44:19 +01:00
user fix(roles): Default to root as user name 2025-03-16 17:44:19 +01:00
wayland ref(roles): All roles use desired package state 2025-03-13 11:24:14 +01:00