Gilles Dartiguelongue e0ed6b6e77 Kill create_cluster pillar switch, refs: #100 ... It is just a variant of init_db. A more correct solution would be to support configuring a different initdb command while passing values from the pillar by default like version. This would make it truly generic but is probably not achievable given current pillar self-referencing capabilities (ie. none). Thus, I decided to make it OS family specific since Debian provides its own tools to manage clusters, etc. Gentoo also has a specific way to initialize a new cluster which does not fit with commands.initdb so the current if/elif would be extended when support is added for Gentoo.		2016-06-07 12:00:50 +02:00
..
client.sls	small refactoring	2015-11-23 14:50:51 +03:00
codenamemap.yaml	Set pkg_dev for all debian variants	2016-06-06 14:45:27 +02:00
defaults.yaml	Kill create_cluster pillar switch, refs: #100	2016-06-07 12:00:50 +02:00
dev.sls	small refactoring	2015-11-23 14:50:51 +03:00
dropped.sls	add dropped state	2015-11-23 14:27:40 +03:00
init.sls	Kill create_cluster pillar switch, refs: #100	2016-06-07 12:00:50 +02:00
map.jinja	Explicitly list the grain that we're filtering by	2016-05-23 15:02:26 -04:00
osmap.yaml	Kill create_cluster pillar switch, refs: #100	2016-06-07 12:00:50 +02:00
pg_hba.conf	Limitation of default access rights to improve security	2015-01-12 19:02:06 +01:00
python.sls	Change states to use short-dec style	2014-12-13 00:19:59 -07:00
upstream.sls	Upstream repo for RedHat	2016-02-20 14:12:08 +00:00