Stop using clean: True on /etc/salt/{minion,master}.d

New versions of Salt put config files in /etc/salt/{minion,master}.d. We don't
want to erase them by using a clean: True on the file.recurse. This is a
backward incompatible change, but it's necessary to avoid deleting Salt config
files.

Resolves #104

pillar.example

 salt:
+  clean_config_d_dir: False
 
   # to overwrite map.jinja salt packages
   lookup:
       ssl_key: /etc/pki/api/certs/server.key
       debug: False
       disable_ssl: False
- 
+
   # salt minion config:
   minion:
 
     # single master setup
     master: salt
-    
+
     # multi master setup
     master:
       - salt_master_1
       - salt_master_2
-    
+
     fileserver_backend:
       - git
       - roots

salt/defaults.yaml

   salt_cloud: salt-cloud
   salt_api: salt-api
   salt_ssh: salt-ssh
+  clean_config_d_dir: False

salt/master.sls

     - name: {{ salt_settings.config_path }}/master.d
     - template: jinja
     - source: salt://salt/files/master.d
-    - clean: True
+    - clean: {{ salt_settings.clean_config_d_dir }}
   service.running:
     - enable: True
     - name: {{ salt_settings.master_service }}

salt/minion.sls

     - name: {{ salt_settings.config_path }}/minion.d
     - template: jinja
     - source: salt://salt/files/minion.d
-    - clean: True
+    - clean: {{ salt_settings.clean_config_d_dir }}
     - context:
         standalone: False
   service.running:

salt/standalone.sls

     - name: {{ salt_settings.config_path }}/minion.d
     - template: jinja
     - source: salt://salt/files/minion.d
-    - clean: True
+    - clean: {{ salt_settings.clean_config_d_dir }}
     - context:
         standalone: True
   service.dead: