Salt
/
salt-formula
mirror of https://github.com/saltstack-formulas/salt-formula.git
0
0
Fork 0
Code Issues Activity
salt-formula/salt/standalone.sls

41 lines
1.2 KiB
Plaintext
Raw Normal View History

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 }}
fix(gentoo): use `retry_options` to avoid spurious service failures Use the `retry_options` on Gentoo, similar to how its already being used across the state files for FreeBSD, since we're getting failures such as this one: * https://gitlab.com/myii/salt-formula/-/jobs/2285180374
2022-04-03 11:26:20 +02:00
{%- if grains.os_family in ['FreeBSD', 'Gentoo'] %}
fix(freebsd): use `retry_options` to avoid spurious service failures Use the `retry_options` already being used for the Salt minion service, since we're getting failures such as this one: * https://github.com/myii/salt-formula/runs/2415072504 This is made worse by the fact that GitHub Actions cannot re-run a single job (at the current time).
2021-04-23 10:13:59 +02:00
- retry: {{ salt_settings.retry_options | json }}
{%- endif %}
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