Salt tools give a nice way to configure system (make sure templates exist with certain packages, prepare AppVMs based on them, etc). But I'd prefer to edit them in a customized editor, with syntax highlighting, etc, which is strongly discouraged from being put into dom0. I also feel that having version control over those files is the way to go, preferably synced somewhere so I can for example easily replicate this when setting up another computer or reinstalling.
My understanding is that this is a perfect use case for new Admin API - have a machine with editor and git set up to adjust salt files, and either give admin permissions to that one, or use something like split-git that was mentioned to pull the repo into another VM and execute there. Am I on the right track here? If so: 1) What packages do I need on admin VM to be able to do this? 2) Where and how should I be executing this? A quick test of running qubesctl inside a VM didn't even produce logs in dom0 journal, the command just complained it can't reach a daemon. 3) What would be a good way to track and distribute necessary changes to /etc/qubes-rpc/policy/ on dom0? And if I'm not on the right track, then what would be the proper way to approach this? -- viq -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CALF8MVFrdUM4LoR-FD3pT3MRrLHBRRYNVHdxjYdoTEkKCQQc%3Dw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
