I'm working to make SALT more accessible ([#8218](https://github.com/QubesOS/qubes-issues/issues/8218)) and ensure user SALT states are backed up by default ([#8853](https://github.com/QubesOS/qubes-issues/issues/8853)).
It seems the user environment was introduced 10 years ago somewhere around [qubes-mgmt-salt commit 1890a4e7ec77009b81faecaa25606dfee2e7633e by nrgaway](https://github.com/QubesOS/qubes-mgmt-salt/commit/1890a4e7ec77009b81faecaa25606dfee2e7633e). Having another env seems to add subtle complexity. What is the advantage to having a user env instead of just a user directory in the base env? I wouldn't suggest we add multiple file_roots to the base env, because you then have the potential of [colliding subdirectory names causing confusion](https://docs.saltproject.io/en/latest/ref/configuration/master.html#file-roots). But why not add a /srv/salt/user/ directory? The only downside I see there would be that users would have to prefix their states with user. Also, I have found debugging SALT to be a nightmare, with critical errors hidden under DEBUG. Is this something Qubes-specific? E.g. because there is output in a management disp VM that I am not seeing? If so, what is the easiest way to debug SALT scripts in Qubes? -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/qubes-devel/auQRFN2mgEDVemsMt6AmtWLzSylG0v7hbTR9RjdaEYa_sCfT9KBWhMSVvT6gYdqgyYcCQZNOeEy3Qnk5nhN85zhjHZdqx_5rqaISxH3OwmQ%3D%40zazbrown.com.
