salt-formula/salt/standalone.sls

{%- set tplroot = tpldir.split('/')[0] %}
{% from "salt/map.jinja" import salt_settings with context %}

salt-minion-standalone:
  {% if salt_settings.install_packages %}
  pkg.installed:
    - name: {{ salt_settings.salt_minion }}
     {%- if salt_settings.version is defined %}
    - version: {{ salt_settings.version }}
     {%- endif %}
  {% endif %}
  file.recurse:
    - name: {{ salt_settings.config_path }}/minion.d
    - template: jinja
    - source: salt://{{ tplroot }}/files/minion.d
    - clean: {{ salt_settings.clean_config_d_dir }}
    - exclude_pat: _*
    - context:
        standalone: True
  {%- if not salt_settings.minion.master_type %}
  service.running:
    - enable: True
  {%- else %}
  service.dead:
    - enable: False
  {%- endif %}
    - name: {{ salt_settings.minion_service }}
    - require:
  {% if salt_settings.install_packages %}
      - pkg: salt-minion-standalone
  {% endif %}
      - file: salt-minion-standalone

# clean up old _defaults.conf file if they have it around
remove-old-standalone-conf-file:
  file.absent:
    - name: {{ salt_settings.config_path }}/minion.d/_defaults.conf
fix(tpl_path): replace slspath to tplroot 2020-02-12 05:49:22 +01:00			`{%- set tplroot = tpldir.split('/')[0] %}`
Don't overwrite salt variable Using a variable named salt is a bad idea when salt already has a variable named salt. 2015-03-17 05:39:32 +01:00			`{% from "salt/map.jinja" import salt_settings with context %}`
Add a “salt.standalone” state 2014-12-21 15:35:45 +01:00
feat(metastate): add metastate per community convention 2020-02-18 14:34:38 +01:00			`salt-minion-standalone:`
			`{% if salt_settings.install_packages %}`
Add a “salt.standalone” state 2014-12-21 15:35:45 +01:00			`pkg.installed:`
Don't overwrite salt variable Using a variable named salt is a bad idea when salt already has a variable named salt. 2015-03-17 05:39:32 +01:00			`- name: {{ salt_settings.salt_minion }}`
feat(metastate): add metastate per community convention 2020-02-18 14:34:38 +01:00			`{%- if salt_settings.version is defined %}`
Add configuration for packages version 2018-02-01 11:13:55 +01:00			`- version: {{ salt_settings.version }}`
feat(metastate): add metastate per community convention 2020-02-18 14:34:38 +01:00			`{%- endif %}`
			`{% endif %}`
Add a “salt.standalone” state 2014-12-21 15:35:45 +01:00			`file.recurse:`
Don't overwrite salt variable Using a variable named salt is a bad idea when salt already has a variable named salt. 2015-03-17 05:39:32 +01:00			`- name: {{ salt_settings.config_path }}/minion.d`
Add a “salt.standalone” state 2014-12-21 15:35:45 +01:00			`- template: jinja`
fix(tpl_path): replace slspath to tplroot 2020-02-12 05:49:22 +01:00			`- source: salt://{{ tplroot }}/files/minion.d`
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 2015-03-23 22:53:24 +01:00			`- clean: {{ salt_settings.clean_config_d_dir }}`
Switch config file.recurse to clean by default and tell it to ignore _* Salt writes it's schedule file to /etc/salt/{minion,master}.d/_schedule.conf We don't want to stomp all over Salt's files, but we do want a pristine starting point to lay down our managed config. So we use clean: True on the file.recurse call, but we tell it to ignore files that start with an _ We have to rename the current config file (_defaults.conf) because it will be ignored by the rule that ignores Salt's _* config files. This also means we need to clean up old config files (_defaults.conf) and restart the service if we cleaned it up. 2015-03-27 23:58:05 +01:00			`- exclude_pat: _*`
Add a “salt.standalone” state 2014-12-21 15:35:45 +01:00			`- context:`
			`standalone: True`
feat(metastate): add metastate per community convention 2020-02-18 14:34:38 +01:00			`{%- if not salt_settings.minion.master_type %}`
add option to start minion service if master_type is set to disable 2016-10-01 09:30:39 +02:00			`service.running:`
fix minion daemon to be enabled if master_type is set to disable 2016-10-01 11:31:56 +02:00			`- enable: True`
feat(metastate): add metastate per community convention 2020-02-18 14:34:38 +01:00			`{%- else %}`
Add a “salt.standalone” state 2014-12-21 15:35:45 +01:00			`service.dead:`
			`- enable: False`
feat(metastate): add metastate per community convention 2020-02-18 14:34:38 +01:00			`{%- endif %}`
Don't overwrite salt variable Using a variable named salt is a bad idea when salt already has a variable named salt. 2015-03-17 05:39:32 +01:00			`- name: {{ salt_settings.minion_service }}`
Add a “salt.standalone” state 2014-12-21 15:35:45 +01:00			`- require:`
feat(metastate): add metastate per community convention 2020-02-18 14:34:38 +01:00			`{% if salt_settings.install_packages %}`
			`- pkg: salt-minion-standalone`
			`{% endif %}`
			`- file: salt-minion-standalone`
Switch config file.recurse to clean by default and tell it to ignore _* Salt writes it's schedule file to /etc/salt/{minion,master}.d/_schedule.conf We don't want to stomp all over Salt's files, but we do want a pristine starting point to lay down our managed config. So we use clean: True on the file.recurse call, but we tell it to ignore files that start with an _ We have to rename the current config file (_defaults.conf) because it will be ignored by the rule that ignores Salt's _* config files. This also means we need to clean up old config files (_defaults.conf) and restart the service if we cleaned it up. 2015-03-27 23:58:05 +01:00
			`# clean up old _defaults.conf file if they have it around`
			`remove-old-standalone-conf-file:`
			`file.absent:`
Replace absolute config pathname prefixes with the config_path variable 2016-03-29 19:28:47 +02:00			`- name: {{ salt_settings.config_path }}/minion.d/_defaults.conf`