On 9/13/20 6:57 PM, [email protected] wrote:
OK, it might have been better if you had NOT modified my example, as you should then have been able to verify that user pillars can be referenced in this way. I always find it better to take one small step at a time when troubleshooting or trying to learn something new. In the new case, you are using the user environment. I would try the following: /srv/salt/user_salt/get.top user: target: - get /srv/salt/user_salt/get.sls get file: cmd.run: - name: wget {{pillar['host'] }} qubesctl --skip-dom0 --targets=target state.apply saltenv=user get You might like to look at: https://docs.saltstack.com/en/latest/ref/states/top.html#environments New environments can be defined in `/etc/salt/minions.d/f_defaults.conf`, but I rarely do this in Qubes.unman, as always you pointed me into the right direction. The whole reason it was not working as I missed up with the directories. Instead of using: /srv/user_salt I was using: /srv/salt/user_salt That's why your first example didn't work in my environment and I had to adjust it. Now everything is running perfectly with user defined pillars! Thank you very much!
I also got this running, thanks! However when I run qubesctl --all --show-output state.highstate saltenv=user I get for my states: State 'qvm.present' was not found in SLS 'mysls' Reason: 'qvm.present' is not available. I guess the custom qvm.* states are not available in the /srv/user_salt folder, but only in /srv/salt? Is there any way to make them available in /srv/user_salt as well? Side Note: I ran `qubesctl --show-output state.sls qubes.user-dirs` to obtain the folders. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/94f4ae21-bc4e-d1e6-38ce-94b753ef6437%40hackingthe.net.
smime.p7s
Description: S/MIME Cryptographic Signature
