Hi Am Dienstag, 21. April 2020, 21:21:33 CEST schrieb Mattias Giese:
Heya,
On 21/04/20 14:01:49, Steve Moring wrote:
I'd like to deliver /etc/motd to clients
I see https://www.uyuni-project.org/uyuni-docs/uyuni/salt/salt-states.html
...and pillars.
Do I create a state channel or config channel?
That depends on what you are trying to achieve. If you simply need to deploy a static file a config channel is sufficient. If you want to deploy a template or do anything besides static file deployment you need to create a state channel. Take note that the old {| rhn_macros |}-scheme will not work with Salt clients.
Correct. The normal Config Channels are just the same as you have in spacewalk and it is now working for traditional and salt clients. You can assign both to the same channel. With the exception of the macros as salt uses a different templating mechanism. State Channels are pure salt but you can do even more as you write the state file on your own. You can deploy configuration files, modify files on the system, run commands, install, update, remove packages, etc. Everything what salt states provide. https://docs.saltstack.com/en/master/py-modindex.html#cap-s (see salt.states.*) -- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org