Hi Strahil, I have a small addition to Silvio's answer: if you don't want to call the whole highstate in the cron job, you can just apply the state that corresponds to the configuration channel which contains your configuration file. Each configuration channel creates a salt state that you can use, although its name is not visible in the UI (yet). The naming scheme of the generated states is as follows: manager_org_<your-org-id>.<config-channel-label> So if your motd file is in configuration channel with label 'motd-config' and your organization id is 1, then you can apply the state locally on the minion using this command: salt-call state.apply manager_org_1.motd-config HTH, Franky. Strahil Nikolov writes:
Hello Community,
I have setup a system with a centrally managed configuration file (/etc/motd) and when applying high state - it gets deployed.
I checked the taskomatic and there is a job for checking (compare-configs-default) which properly detects a difference from centrally managed file and local one .
Can someone hint me , how can I schedule a task so the files that diff to be replaced with the centrally managed one (from uyuni) - so if I edit /etc/motd locally -> the file to be restored on a schedule ?
If there is no such option , is it currently under development ?
Thanks in advance.
Best Regards, Strahil Nikolov
-- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org