salt-formula/salt/files/master

# This file managed by Salt, do not edit by hand!!
#  Based on salt version 0.17.4 default config
{% set salt = pillar.get('salt', {}) -%}
{% set master = salt.get('master', {}) -%}
{%- macro get_config(configname, default_value) -%}
{%- if configname in master -%}
{{ configname }}: {{ master[configname] }}
{%- elif configname in salt -%}
{{ configname }}: {{ salt[configname] }}
{%- else -%}
#{{ configname }}: {{ default_value }}
{%- endif -%}
{%- endmacro -%}
##### Primary configuration settings #####
##########################################
# This configuration file is used to manage the behavior of the Salt Master
# Values that are commented out but have no space after the comment are
# defaults that need not be set in the config. If there is a space after the
# comment that the value is presented as an example and is not the default.

# Per default, the master will automatically include all config files
# from master.d/*.conf (master.d is a directory in the same directory
# as the main master config file)
{{ get_config('default_include', 'master.d/*.conf') }}

# The address of the interface to bind to
{{ get_config('interface', '0.0.0.0') }}

# Whether the master should listen for IPv6 connections. If this is set to True,
# the interface option must be adjusted too (for example: "interface: '::'")
{{ get_config('ipv6', 'False') }}

# The tcp port used by the publisher
{{ get_config('publish_port', '4505') }}

# The user to run the salt-master as. Salt will update all permissions to
# allow the specified user to run the master. If the modified files cause
# conflicts set verify_env to False.
{{ get_config('user', 'root') }}

# Max open files
# Each minion connecting to the master uses AT LEAST one file descriptor, the
# master subscription connection. If enough minions connect you might start
# seeing on the console(and then salt-master crashes):
#   Too many open files (tcp_listener.cpp:335)
#   Aborted (core dumped)
#
# By default this value will be the one of `ulimit -Hn`, ie, the hard limit for
# max open files.
#
# If you wish to set a different value than the default one, uncomment and
# configure this setting. Remember that this value CANNOT be higher than the
# hard limit. Raising the hard limit depends on your OS and/or distribution,
# a good way to find the limit is to search the internet for(for example):
#   raise max open files hard limit debian
#
{{ get_config('max_open_files', '100000') }}

# The number of worker threads to start, these threads are used to manage
# return calls made from minions to the master, if the master seems to be
# running slowly, increase the number of threads
{{ get_config('worker_threads', '5') }}

# The port used by the communication interface. The ret (return) port is the
# interface used for the file server, authentication, job returnes, etc.
{{ get_config('ret_port', '4506') }}

# Specify the location of the daemon process ID file
{{ get_config('pidfile', '/var/run/salt-master.pid') }}

# The root directory prepended to these options: pki_dir, cachedir,
# sock_dir, log_file, autosign_file, autoreject_file, extension_modules,
# key_logfile, pidfile.
{{ get_config('root_dir', '/') }}

# Directory used to store public key data
{{ get_config('pki_dir', '/etc/salt/pki/master') }}

# Directory to store job and cache data
{{ get_config('cachedir', '/var/cache/salt/master') }}

# Verify and set permissions on configuration directories at startup
{{ get_config('verify_env', 'True') }}

# Set the number of hours to keep old job information in the job cache
{{ get_config('keep_jobs', '24') }}

# Set the default timeout for the salt command and api, the default is 5
# seconds
{{ get_config('timeout', '5') }}

# The loop_interval option controls the seconds for the master's maintenance
# process check cycle. This process updates file server backends, cleans the
# job cache and executes the scheduler.
{{ get_config('loop_interval', '60') }}

# Set the default outputter used by the salt command. The default is "nested"
{{ get_config('output', 'nested') }}

# By default output is colored, to disable colored output set the color value
# to False
{{ get_config('color', 'True') }}

# Set the directory used to hold unix sockets
{{ get_config('sock_dir', '/var/run/salt/master') }}

# The master can take a while to start up when lspci and/or dmidecode is used
# to populate the grains for the master. Enable if you want to see GPU hardware
# data for your master.
#
{{ get_config('enable_gpu_grains', 'False') }}

# The master maintains a job cache, while this is a great addition it can be
# a burden on the master for larger deployments (over 5000 minions).
# Disabling the job cache will make previously executed jobs unavailable to
# the jobs system and is not generally recommended.
#
{{ get_config('job_cache', 'True') }}

# Cache minion grains and pillar data in the cachedir.
{{ get_config('minion_data_cache', 'True') }}

# The master can include configuration from other files. To enable this,
# pass a list of paths to this option. The paths can be either relative or
# absolute; if relative, they are considered to be relative to the directory
# the main master configuration file lives in (this file). Paths can make use
# of shell-style globbing. If no files are matched by a path passed to this
# option then the master will log a warning message.
#
#
# Include a config file from some other path:
#include: /etc/salt/extra_config
#
# Include config from several files and directories:
#include:
#  - /etc/salt/extra_config
{{ get_config('include', '[]') }}


#####        Security settings       #####
##########################################
# Enable "open mode", this mode still maintains encryption, but turns off
# authentication, this is only intended for highly secure environments or for
# the situation where your keys end up in a bad state. If you run in open mode
# you do so at your own risk!
{{ get_config('open_mode', 'False') }}

# Enable auto_accept, this setting will automatically accept all incoming
# public keys from the minions. Note that this is insecure.
{{ get_config('auto_accept', 'False') }}

# If the autosign_file is specified, incoming keys specified in the
# autosign_file will be automatically accepted. This is insecure.  Regular
# expressions as well as globing lines are supported.
{{ get_config('autosign_file', '/etc/salt/autosign.conf') }}

# Works like autosign_file, but instead allows you to specify minion IDs for
# which keys will automatically be rejected. Will override both membership in
# the autosign_file and the auto_accept setting.
{{ get_config('autorejecte_file', '/etc/salt/autosign.conf') }}

# Enable permissive access to the salt keys.  This allows you to run the
# master or minion as root, but have a non-root group be given access to
# your pki_dir.  To make the access explicit, root must belong to the group
# you've given access to.  This is potentially quite insecure.
# If an autosign_file is specified, enabling permissive_pki_access will allow group access
# to that specific file.
{{ get_config('permissive_pki_access', 'False') }}

# Allow users on the master access to execute specific commands on minions.
# This setting should be treated with care since it opens up execution
# capabilities to non root users. By default this capability is completely
# disabled.
#
#client_acl:
#  larry:
#    - test.ping
#    - network.*
#
{{ get_config('client_acl', '{}') }}

# Blacklist any of the following users or modules
#
# This example would blacklist all non sudo users, including root from
# running any commands. It would also blacklist any use of the "cmd"
# module.
# This is completely disabled by default.
#
{% if 'client_acl_blacklist' in master -%}
client_acl_blacklist:
  users:
  {% for user in master['client_acl_blacklist'].get('users', []) -%}
    - {{ user }}
  {% endfor -%}
  modules:
  {% for mod in master['client_acl_blacklist'].get('modules', []) -%}
    - {{ mod }}
  {% endfor -%}
{% elif 'client_acl_blacklist' in salt  -%}
client_acl_blacklist:
  users:
  {% for user in salt['client_acl_blacklist'].get('users', []) -%}
    - {{ user }}
  {% endfor -%}
  modules:
  {% for mod in salt['client_acl_blacklist'].get('modules', []) -%}
    - {{ mod }}
  {% endfor -%}
{% else -%}
#client_acl_blacklist:
#  users:
#    - root
#    - '^(?!sudo_).*$'   #  all non sudo users
#  modules:
#    - cmd
{%- endif %}

# The external auth system uses the Salt auth modules to authenticate and
# validate users to access areas of the Salt system.
#
#external_auth:
#  pam:
#    fred:
#      - test.*
#
{{ get_config('external_auth', '{}') }}

# Time (in seconds) for a newly generated token to live. Default: 12 hours
{{ get_config('token_expire', '43200') }}

# Allow minions to push files to the master. This is disabled by default, for
# security purposes.
{{ get_config('file_recv', 'False') }}

# Set a hard-limit on the size of the files that can be pushed to the master.
# It will be interpreted as megabytes.
# Default: 100
{{ get_config('file_recv_max_size', '100') }}

# Signature verification on messages published from the master.
# This causes the master to cryptographically sign all messages published to its event
# bus, and minions then verify that signature before acting on the message.
#
# This is False by default.
#
# Note that to facilitate interoperability with masters and minions that are different
# versions, if sign_pub_messages is True but a message is received by a minion with
# no signature, it will still be accepted, and a warning message will be logged.
# Conversely, if sign_pub_messages is False, but a minion receives a signed
# message it will be accepted, the signature will not be checked, and a warning message
# will be logged.  This behavior will go away in Salt 0.17.6 (or Hydrogen RC1, whichever
# comes first) and these two situations will cause minion to throw an exception and
# drop the message.
#
{{ get_config('sign_pub_message', 'False') }}

#####    Master Module Management    #####
##########################################
# Manage how master side modules are loaded

# Add any additional locations to look for master runners
{{ get_config('runner_dirs', '[]') }}

# Enable Cython for master side modules
{{ get_config('cython_enable', 'False') }}


#####      State System settings     #####
##########################################
# The state system uses a "top" file to tell the minions what environment to
# use and what modules to use. The state_top file is defined relative to the
# root of the base environment as defined in "File Server settings" below.
{{ get_config('state_top', 'top.sls') }}

# The master_tops option replaces the external_nodes option by creating
# a plugable system for the generation of external top data. The external_nodes
# option is deprecated by the master_tops option.
# To gain the capabilities of the classic external_nodes system, use the
# following configuration:
# master_tops:
#   ext_nodes: <Shell command which returns yaml>
#
{{ get_config('master_tops', '{}') }}

# The external_nodes option allows Salt to gather data that would normally be
# placed in a top file. The external_nodes option is the executable that will
# return the ENC data. Remember that Salt will look for external nodes AND top
# files and combine the results if both are enabled!
{{ get_config('external_nodes', 'None') }}

# The renderer to use on the minions to render the state data
{{ get_config('renderer', 'yaml_jinja') }}

# The Jinja renderer can strip extra carriage returns and whitespace
# See http://jinja.pocoo.org/docs/api/#high-level-api
#
# If this is set to True the first newline after a Jinja block is removed
# (block, not variable tag!). Defaults to False, corresponds to the Jinja
# environment init variable "trim_blocks".
{{ get_config('jinja_trim_blocks', 'False') }}
#
# If this is set to True leading spaces and tabs are stripped from the start
# of a line to a block. Defaults to False, corresponds to the Jinja
# environment init variable "lstrip_blocks".
{{ get_config('jinja_lstrip_blocks', 'False') }}

# The failhard option tells the minions to stop immediately after the first
# failure detected in the state execution, defaults to False
{{ get_config('failhard', 'False') }}

# The state_verbose and state_output settings can be used to change the way
# state system data is printed to the display. By default all data is printed.
# The state_verbose setting can be set to True or False, when set to False
# all data that has a result of True and no changes will be suppressed.
{{ get_config('state_verbose', 'True') }}

# The state_output setting changes if the output is the full multi line
# output for each changed state if set to 'full', but if set to 'terse'
# the output will be shortened to a single line.  If set to 'mixed', the output
# will be terse unless a state failed, in which case that output will be full.
{{ get_config('state_output', 'full') }}


#####      File Server settings      #####
##########################################
# Salt runs a lightweight file server written in zeromq to deliver files to
# minions. This file server is built into the master daemon and does not
# require a dedicated port.

# The file server works on environments passed to the master, each environment
# can have multiple root directories, the subdirectories in the multiple file
# roots cannot match, otherwise the downloaded files will not be able to be
# reliably ensured. A base environment is required to house the top file.
# Example:
# file_roots:
#   base:
#     - /srv/salt/
#   dev:
#     - /srv/salt/dev/services
#     - /srv/salt/dev/states
#   prod:
#     - /srv/salt/prod/services
#     - /srv/salt/prod/states
{% if 'file_roots' in master -%}
file_roots:
  {% for name, roots in master['file_roots'].items() -%}
  {{ name }}:
    {% for dir in roots -%}
      - {{ dir }}
    {% endfor -%}
  {% endfor -%}
{% elif 'file_roots' in salt -%}
file_roots:
  {% for name, roots in salt['file_roots'].items() -%}
  {{ name }}:
    {% for dir in roots -%}
      - {{ dir }}
    {% endfor -%}
  {% endfor -%}
{% else -%}
#file_roots:
#  base:
#    - /srv/salt
{%- endif %}

# The hash_type is the hash to use when discovering the hash of a file on
# the master server. The default is md5, but sha1, sha224, sha256, sha384
# and sha512 are also supported.
{{ get_config('hash_type', 'md5') }}

# The buffer size in the file server can be adjusted here:
{{ get_config('file_buffer_size', '1048576') }}

# A regular expression (or a list of expressions) that will be matched
# against the file path before syncing the modules and states to the minions.
# This includes files affected by the file.recurse state.
# For example, if you manage your custom modules and states in subversion
# and don't want all the '.svn' folders and content synced to your minions,
# you could set this to '/\.svn($|/)'. By default nothing is ignored.
{% if 'file_ignore_regex' in master -%}
file_ignore_regex:
  {% for regex in master['file_ignore_regex'] -%}
  - {{ regex }}
  {% endfor -%}
{% elif 'file_ignore_regex' in salt -%}
file_ignore_regex:
  {% for regex in salt['file_ignore_regex'] -%}
  - {{ regex }}
  {% endfor -%}
{% else -%}
#file_ignore_regex:
#  - '/\.svn($|/)'
#  - '/\.git($|/)'
{%- endif %}

# A file glob (or list of file globs) that will be matched against the file
# path before syncing the modules and states to the minions. This is similar
# to file_ignore_regex above, but works on globs instead of regex. By default
# nothing is ignored.
{% if 'file_ignore_glob' in master -%}
file_ignore_glob:
  {% for glob in master['file_ignore_glob'] -%}
  - {{ glob }}
  {% endfor -%}
{% elif 'file_ignore_glob' in salt -%}
file_ignore_glob:
  {% for glob in salt['file_ignore_glob'] -%}
  - {{ glob }}
  {% endfor -%}
{% else -%}
# file_ignore_glob:
#  - '*.pyc'
#  - '*/somefolder/*.bak'
#  - '*.swp'
{%- endif %}

# File Server Backend
# Salt supports a modular fileserver backend system, this system allows
# the salt master to link directly to third party systems to gather and
# manage the files available to minions. Multiple backends can be
# configured and will be searched for the requested file in the order in which
# they are defined here. The default setting only enables the standard backend
# "roots" which uses the "file_roots" option.
#
#fileserver_backend:
#  - roots
#
# To use multiple backends list them in the order they are searched:
#
#fileserver_backend:
#  - git
#  - roots
{% if 'fileserver_backend' in master -%}
fileserver_backend:
{%- for backend in master['fileserver_backend'] %}
  - {{ backend }}
{% endfor -%}
{% endif %}
#
# Uncomment the line below if you do not want the file_server to follow
# symlinks when walking the filesystem tree. This is set to True
# by default. Currently this only applies to the default roots
# fileserver_backend.
#
{{ get_config('fileserver_followsymlinks', 'False') }}
#
# Uncomment the line below if you do not want symlinks to be
# treated as the files they are pointing to. By default this is set to
# False. By uncommenting the line below, any detected symlink while listing
# files on the Master will not be returned to the Minion.
#
{{ get_config('fileserver_ignoresymlinks', 'True') }}

#
# By default, the Salt fileserver recurses fully into all defined environments
# to attempt to find files. To limit this behavior so that the fileserver only
# traverses directories with SLS files and special Salt directories like _modules,
# enable the option below. This might be useful for installations where a file root
# has a very large number of files and performance is impacted. Default is False.
#
{{ get_config('fileserver_limit_traversal', 'False') }}
#
# The fileserver can fire events off every time the fileserver is updated,
# these are disabled by default, but can be easily turned on by setting this
# flag to True
{{ get_config('fileserver_events', 'False') }}
#
# Git fileserver backend configuration
#
# Gitfs can be provided by one of two python modules: GitPython or pygit2. If
# using pygit2, both libgit2 and git must also be installed.
{{ get_config('gitfs_provider', 'gitpython') }}
#
# When using the git fileserver backend at least one git remote needs to be
# defined. The user running the salt master will need read access to the repo.
#
# The repos will be searched in order to find the file requested by a client
# and the first repo to have the file will return it.
# When using the git backend branches and tags are translated into salt
# environments.
# Note:  file:// repos will be treated as a remote, so refs you want used must
# exist in that repo as *local* refs.
{% if 'gitfs_remotes' in master -%}
gitfs_remotes:
{%- for remote in master['gitfs_remotes'] %}
  - {{ remote }}{% endfor -%}
{%- endif %}
#
#gitfs_remotes:
#  - git://github.com/saltstack/salt-states.git
#  - file:///var/git/saltmaster
#
# The gitfs_ssl_verify option specifies whether to ignore ssl certificate
# errors when contacting the gitfs backend. You might want to set this to
# false if you're using a git backend that uses a self-signed certificate but
# keep in mind that setting this flag to anything other than the default of True
# is a security concern, you may want to try using the ssh transport.
{{ get_config('gitfs_ssl_verify', 'True') }}
#
#
# The gitfs_root option gives the ability to serve files from a subdirectory
# within the repository. The path is defined relative to the root of the
# repository and defaults to the repository root.
{{ get_config('gitfs_root', 'somefolder/otherfolder') }}


#####         Pillar settings        #####
##########################################
# Salt Pillars allow for the building of global data that can be made selectively
# available to different minions based on minion grain filtering. The Salt
# Pillar is laid out in the same fashion as the file server, with environments,
# a top file and sls files. However, pillar data does not need to be in the
# highstate format, and is generally just key/value pairs.
{% if 'pillar_roots' in master -%}
pillar_roots:
  {% for name, roots in master['pillar_roots'].items() -%}
  {{ name }}:
    {% for dir in roots -%}
      - {{ dir }}
    {% endfor -%}
  {% endfor -%}
{% elif 'pillar_roots' in salt -%}
pillar_roots:
  {% for name, roots in salt['pillar_roots'].items() -%}
  {{ name }}:
    {% for dir in roots -%}
      - {{ dir }}
    {% endfor -%}
  {% endfor -%}
{% else %}
#pillar_roots:
#  base:
#    - /srv/pillar
{%- endif %}

{% if 'ext_pillar' in master -%}
ext_pillar:
{% for pillar in master['ext_pillar'] %}
  - {{ pillar.items()[0][0] }}: {{ pillar.items()[0][1] }}
{% endfor -%}
{% elif 'ext_pillar' in salt -%}
ext_pillar:
{% for pillar in salt['ext_pillar'] %}
  - {{ pillar.items()[0][0] }}: {{ pillar.items()[0][1] }}
{% endfor -%}
{% else %}
#ext_pillar:
#  - hiera: /etc/hiera.yaml
#  - cmd_yaml: cat /etc/salt/yaml
{%- endif %}

# The pillar_gitfs_ssl_verify option specifies whether to ignore ssl certificate
# errors when contacting the pillar gitfs backend. You might want to set this to
# false if you're using a git backend that uses a self-signed certificate but
# keep in mind that setting this flag to anything other than the default of True
# is a security concern, you may want to try using the ssh transport.
{{ get_config('pillar_gitfs_ssl_verify', 'True') }}

# The pillar_opts option adds the master configuration file data to a dict in
# the pillar called "master". This is used to set simple configurations in the
# master config file that can then be used on minions.
{{ get_config('pillar_opts', 'True') }}


#####          Syndic settings       #####
##########################################
# The Salt syndic is used to pass commands through a master from a higher
# master. Using the syndic is simple, if this is a master that will have
# syndic servers(s) below it set the "order_masters" setting to True, if this
# is a master that will be running a syndic daemon for passthrough the
# "syndic_master" setting needs to be set to the location of the master server
# to receive commands from.

# Set the order_masters setting to True if this master will command lower
# masters' syndic interfaces.
{{ get_config('order_masters', 'False') }}

# If this master will be running a salt syndic daemon, syndic_master tells
# this master where to receive commands from.
{{ get_config('syndic_master', 'masterofmaster') }}

# This is the 'ret_port' of the MasterOfMaster
{{ get_config('syndic_master_port', '4506') }}

# PID file of the syndic daemon
{{ get_config('syndic_pidfile', '/var/run/salt-syndic.pid') }}

# LOG file of the syndic daemon
{{ get_config('syndic_log_file', 'syndic.log') }}

#####      Peer Publish settings     #####
##########################################
# Salt minions can send commands to other minions, but only if the minion is
# allowed to. By default "Peer Publication" is disabled, and when enabled it
# is enabled for specific minions and specific commands. This allows secure
# compartmentalization of commands based on individual minions.

# The configuration uses regular expressions to match minions and then a list
# of regular expressions to match functions. The following will allow the
# minion authenticated as foo.example.com to execute functions from the test
# and pkg modules.
#
#peer:
#  foo.example.com:
#    - test.*
#    - pkg.*
#
# This will allow all minions to execute all commands:
#
#peer:
#  .*:
#    - .*
#
# This is not recommended, since it would allow anyone who gets root on any
# single minion to instantly have root on all of the minions!
{% if 'peer' in master -%}
peer:
  {% for name, roots in master['peer'].items() -%}
  {{ name }}:
    {% for mod in roots -%}
      - {{ mod }}
    {% endfor -%}
  {% endfor -%}
{% elif 'peer' in salt -%}
peer:
  {% for name, roots in salt['peer'].items() -%}
  {{ name }}:
    {% for mod in roots -%}
      - {{ mod }}
    {% endfor -%}
  {% endfor -%}
{% endif -%}

# Minions can also be allowed to execute runners from the salt master.
# Since executing a runner from the minion could be considered a security risk,
# it needs to be enabled. This setting functions just like the peer setting
# except that it opens up runners instead of module functions.
#
# All peer runner support is turned off by default and must be enabled before
# using. This will enable all peer runners for all minions:
#
#peer_run:
#  .*:
#    - .*
#
# To enable just the manage.up runner for the minion foo.example.com:
#
#peer_run:
#  foo.example.com:
#    - manage.up
{% if 'peer_run' in master -%}
peer_run:
  {% for name, roots in master['peer_run'].items() -%}
  {{ name }}:
    {% for mod in roots -%}
      - {{ mod }}
    {% endfor -%}
  {% endfor -%}
{% elif 'peer_run' in salt -%}
peer_run:
  {% for name, roots in salt['peer_run'].items() -%}
  {{ name }}:
    {% for mod in roots -%}
      - {{ mod }}
    {% endfor -%}
  {% endfor -%}
{% endif -%}

#####         Mine settings     #####
##########################################
# Restrict mine.get access from minions. By default any minion has a full access
# to get all mine data from master cache. In acl definion below, only pcre matches
# are allowed.
#
# mine_get:
#   .*:
#     - .*
#
# Example below enables minion foo.example.com to get  'network.interfaces' mine data only
# , minions web* to get all network.* and disk.* mine data and all other minions won't get
# any mine data.
#
# mine_get:
#   foo.example.com:
#     - network.inetrfaces
#   web.*:
#     - network.*
#     - disk.*

#####         Logging settings       #####
##########################################
# The location of the master log file
# The master log can be sent to a regular file, local path name, or network
# location. Remote logging works best when configured to use rsyslogd(8) (e.g.:
# ``file:///dev/log``), with rsyslogd(8) configured for network logging. The URI
# format is: <file|udp|tcp>://<host|socketpath>:<port-if-required>/<log-facility>
#log_file: /var/log/salt/master
#log_file: file:///dev/log
#log_file: udp://loghost:10514

{{ get_config('log_file', '/var/log/salt/master') }}
{{ get_config('key_logfile', '/var/log/salt/key') }}

# The level of messages to send to the console.
# One of 'garbage', 'trace', 'debug', info', 'warning', 'error', 'critical'.
{{ get_config('log_level', 'warning') }}

# The level of messages to send to the log file.
# One of 'garbage', 'trace', 'debug', info', 'warning', 'error', 'critical'.
{{ get_config('log_level_logfile', 'warning') }}

# The date and time format used in log messages. Allowed date/time formating
# can be seen here: http://docs.python.org/library/time.html#time.strftime
{{ get_config('log_datefmt', "'%H:%M:%S'") }}
{{ get_config('log_datefmt_logfile', "'%Y-%m-%d %H:%M:%S'") }}

# The format of the console logging messages. Allowed formatting options can
# be seen here: http://docs.python.org/library/logging.html#logrecord-attributes
{{ get_config('log_fmt_console', "'[%(levelname)-8s] %(message)s'") }}
{{ get_config('log_fmt_logfile', "'%(asctime)s,%(msecs)03.0f [%(name)-17s][%(levelname)-8s] %(message)s'") }}

# This can be used to control logging levels more specificically.  This
# example sets the main salt library at the 'warning' level, but sets
# 'salt.modules' to log at the 'debug' level:
#   log_granular_levels:
#     'salt': 'warning',
#     'salt.modules': 'debug'
#
{% if 'log_granular_levels' in master %}
log_granular_levels:
  {% for name, lvl in master['log_granular_levels'] %}
  {{ name }}: {{ lvl }}
  {% endfor -%}
{% elif 'log_granular_levels' in salt %}
log_granular_levels:
  {% for name, lvl in salt['log_granular_levels'] %}
  {{ name }}: {{ lvl }}
  {% endfor -%}
{% else %}
#log_granular_levels: {}
{% endif %}


#####         Node Groups           #####
##########################################
# Node groups allow for logical groupings of minion nodes.
# A group consists of a group name and a compound target.
#
#nodegroups:
#  group1: 'L@foo.domain.com,bar.domain.com,baz.domain.com and bl*.domain.com'
#  group2: 'G@os:Debian and foo.domain.com'
{% if 'nodegroups' in master %}
nodegroups:
  {% for name, lvl in master['nodegroups'] %}
  {{ name }}: {{ lvl }}
  {% endfor -%}
{% elif 'nodegroups' in salt %}
nodegroups:
  {% for name, lvl in salt['nodegroups'] %}
  {{ name }}: {{ lvl }}
  {% endfor -%}
{% endif %}


#####     Range Cluster settings     #####
##########################################
# The range server (and optional port) that serves your cluster information
# https://github.com/grierj/range/wiki/Introduction-to-Range-with-YAML-files
#
{{ get_config('range_server', 'range:80') }}


#####     Windows Software Repo settings #####
##############################################
# Location of the repo on the master
{{ get_config('win_repo', '/srv/salt/win/repo') }}

# Location of the master's repo cache file
{{ get_config('win_repo_mastercachefile', '/srv/salt/win/repo/winrepo.p') }}

# List of git repositories to include with the local repo
{% if 'win_gitrepos' in master %}
win_gitrepos:
  {% for repo in master['win_gitrepos'] %}
  - {{ repo }}
  {% endfor -%}
{% elif 'win_gitrepos' in salt %}
win_gitrepos:
  {% for repo in salt['win_gitrepos'] %}
  - {{ repo }}
  {% endfor -%}
{% else %}
#win_gitrepos:
#  - 'https://github.com/saltstack/salt-winrepo.git'
{% endif %}

{% if 'halite' in master -%}
#####             Halite             #####
##########################################
halite:
  {%- for name, value in master['halite'].iteritems() %}
  {{ name }}: {{ value }}
  {%- endfor %}
{%- endif %}