carpenti c27bfd92b7 make the configuration of engines specific to master or minion ... the engines are now configured using the following pillars: * salt.master.engines * salt.minion.engines instead of a global salt.engines pillar. Note: the pillar.example provided seems to assume this behaviour. (the pillar is salt.master.engines.slack and not salt.engines.slack)		2016-10-05 10:26:36 +02:00
..
cloud.maps.d	Initial add of dummy saltify settings	2014-12-24 08:40:10 +00:00
cloud.profiles.d	ec2/gce profiles/providers are no longer configured if they are not used.	2015-04-17 10:48:47 -04:00
cloud.providers.d	Added version check for provider/driver backwards compatibility	2016-03-31 23:17:35 -07:00
master.d	make the configuration of engines specific to master or minion	2016-10-05 10:26:36 +02:00
minion.d	make the configuration of engines specific to master or minion	2016-10-05 10:26:36 +02:00
gitfs_key.jinja	Cleanup and make closer to the PR submitted for the mainline salt repo master config file	2016-04-20 15:10:55 -04:00
key	Added functionality to state for salt cloud and exampel for EC2 and GCE	2014-07-20 16:59:38 +02:00
roster.jinja	add support for installing salt-ssh and managing the roster file, updated README and pillar.example	2014-10-28 11:45:32 -05:00