"Fossies" - the Fresh Open Source Software Archive

Member "salt-3002.2/conf/minion" (18 Nov 2020, 38702 Bytes) of package /linux/misc/salt-3002.2.tar.gz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. See also the latest Fossies "Diffs" side-by-side code changes report for "minion": 3002.1_vs_3002.2.

    1 ##### Primary configuration settings #####
    2 ##########################################
    3 # This configuration file is used to manage the behavior of the Salt Minion.
    4 # With the exception of the location of the Salt Master Server, values that are
    5 # commented out but have an empty line after the comment are defaults that need
    6 # not be set in the config. If there is no blank line after the comment, the
    7 # value is presented as an example and is not the default.
    8 
    9 # Per default the minion will automatically include all config files
   10 # from minion.d/*.conf (minion.d is a directory in the same directory
   11 # as the main minion config file).
   12 #default_include: minion.d/*.conf
   13 
   14 # Set the location of the salt master server. If the master server cannot be
   15 # resolved, then the minion will fail to start.
   16 #master: salt
   17 
   18 # Set http proxy information for the minion when doing requests
   19 #proxy_host:
   20 #proxy_port:
   21 #proxy_username:
   22 #proxy_password:
   23 
   24 # List of hosts to bypass HTTP proxy. This key does nothing unless proxy_host etc is
   25 # configured, it does not support any kind of wildcards.
   26 #no_proxy: []
   27 
   28 # If multiple masters are specified in the 'master' setting, the default behavior
   29 # is to always try to connect to them in the order they are listed. If random_master
   30 # is set to True, the order will be randomized upon Minion startup instead. This can
   31 # be helpful in distributing the load of many minions executing salt-call requests,
   32 # for example, from a cron job. If only one master is listed, this setting is ignored
   33 # and a warning will be logged.
   34 #random_master: False
   35 
   36 # NOTE: Deprecated in Salt 2019.2.0. Use 'random_master' instead.
   37 #master_shuffle: False
   38 
   39 # Minions can connect to multiple masters simultaneously (all masters
   40 # are "hot"), or can be configured to failover if a master becomes
   41 # unavailable.  Multiple hot masters are configured by setting this
   42 # value to "str".  Failover masters can be requested by setting
   43 # to "failover".  MAKE SURE TO SET master_alive_interval if you are
   44 # using failover.
   45 # Setting master_type to 'disable' lets you have a running minion (with engines and
   46 # beacons) without a master connection
   47 # master_type: str
   48 
   49 # Poll interval in seconds for checking if the master is still there.  Only
   50 # respected if master_type above is "failover". To disable the interval entirely,
   51 # set the value to -1. (This may be necessary on machines which have high numbers
   52 # of TCP connections, such as load balancers.)
   53 # master_alive_interval: 30
   54 
   55 # If the minion is in multi-master mode and the master_type configuration option
   56 # is set to "failover", this setting can be set to "True" to force the minion
   57 # to fail back to the first master in the list if the first master is back online.
   58 #master_failback: False
   59 
   60 # If the minion is in multi-master mode, the "master_type" configuration is set to
   61 # "failover", and the "master_failback" option is enabled, the master failback
   62 # interval can be set to ping the top master with this interval, in seconds.
   63 #master_failback_interval: 0
   64 
   65 # Set whether the minion should connect to the master via IPv6:
   66 #ipv6: False
   67 
   68 # Set the number of seconds to wait before attempting to resolve
   69 # the master hostname if name resolution fails. Defaults to 30 seconds.
   70 # Set to zero if the minion should shutdown and not retry.
   71 # retry_dns: 30
   72 
   73 # Set the number of times to attempt to resolve
   74 # the master hostname if name resolution fails. Defaults to None,
   75 # which will attempt the resolution indefinitely.
   76 # retry_dns_count: 3
   77 
   78 # Set the port used by the master reply and authentication server.
   79 #master_port: 4506
   80 
   81 # The user to run salt.
   82 #user: root
   83 
   84 # The user to run salt remote execution commands as via sudo. If this option is
   85 # enabled then sudo will be used to change the active user executing the remote
   86 # command. If enabled the user will need to be allowed access via the sudoers
   87 # file for the user that the salt minion is configured to run as. The most
   88 # common option would be to use the root user. If this option is set the user
   89 # option should also be set to a non-root user. If migrating from a root minion
   90 # to a non root minion the minion cache should be cleared and the minion pki
   91 # directory will need to be changed to the ownership of the new user.
   92 #sudo_user: root
   93 
   94 # Specify the location of the daemon process ID file.
   95 #pidfile: /var/run/salt-minion.pid
   96 
   97 # The root directory prepended to these options: pki_dir, cachedir, log_file,
   98 # sock_dir, pidfile.
   99 #root_dir: /
  100 
  101 # The path to the minion's configuration file.
  102 #conf_file: /etc/salt/minion
  103 
  104 # The directory to store the pki information in
  105 #pki_dir: /etc/salt/pki/minion
  106 
  107 # Explicitly declare the id for this minion to use, if left commented the id
  108 # will be the hostname as returned by the python call: socket.getfqdn()
  109 # Since salt uses detached ids it is possible to run multiple minions on the
  110 # same machine but with different ids, this can be useful for salt compute
  111 # clusters.
  112 #id:
  113 
  114 # Cache the minion id to a file when the minion's id is not statically defined
  115 # in the minion config. Defaults to "True". This setting prevents potential
  116 # problems when automatic minion id resolution changes, which can cause the
  117 # minion to lose connection with the master. To turn off minion id caching,
  118 # set this config to ``False``.
  119 #minion_id_caching: True
  120 
  121 # Convert minion id to lowercase when it is being generated. Helpful when some
  122 # hosts get the minion id in uppercase. Cached ids will remain the same and
  123 # not converted. For example, Windows minions often have uppercase minion
  124 # names when they are set up but not always. To turn on, set this config to
  125 # ``True``.
  126 #minion_id_lowercase: False
  127 
  128 # Append a domain to a hostname in the event that it does not exist.  This is
  129 # useful for systems where socket.getfqdn() does not actually result in a
  130 # FQDN (for instance, Solaris).
  131 #append_domain:
  132 
  133 # Custom static grains for this minion can be specified here and used in SLS
  134 # files just like all other grains. This example sets 4 custom grains, with
  135 # the 'roles' grain having two values that can be matched against.
  136 #grains:
  137 #  roles:
  138 #    - webserver
  139 #    - memcache
  140 #  deployment: datacenter4
  141 #  cabinet: 13
  142 #  cab_u: 14-15
  143 #
  144 # Where cache data goes.
  145 # This data may contain sensitive data and should be protected accordingly.
  146 #cachedir: /var/cache/salt/minion
  147 
  148 # Append minion_id to these directories.  Helps with
  149 # multiple proxies and minions running on the same machine.
  150 # Allowed elements in the list: pki_dir, cachedir, extension_modules
  151 # Normally not needed unless running several proxies and/or minions on the same machine
  152 # Defaults to ['cachedir'] for proxies, [] (empty list) for regular minions
  153 #append_minionid_config_dirs:
  154 
  155 # Verify and set permissions on configuration directories at startup.
  156 #verify_env: True
  157 
  158 # The minion can locally cache the return data from jobs sent to it, this
  159 # can be a good way to keep track of jobs the minion has executed
  160 # (on the minion side). By default this feature is disabled, to enable, set
  161 # cache_jobs to True.
  162 #cache_jobs: False
  163 
  164 # Set the directory used to hold unix sockets.
  165 #sock_dir: /var/run/salt/minion
  166 
  167 # In order to calculate the fqdns grain, all the IP addresses from the minion
  168 # are processed with underlying calls to `socket.gethostbyaddr` which can take
  169 # 5 seconds to be released (after reaching `socket.timeout`) when there is no
  170 # fqdn for that IP. These calls to `socket.gethostbyaddr` are processed
  171 # asynchronously, however, it still adds 5 seconds every time grains are
  172 # generated if an IP does not resolve. In Windows grains are regenerated each
  173 # time a new process is spawned. Therefore, the default for Windows is `False`.
  174 # All other OSes default to `True`
  175 # enable_fqdns_grains: True
  176 
  177 # The minion can take a while to start up when lspci and/or dmidecode is used
  178 # to populate the grains for the minion. Set this to False if you do not need
  179 # GPU hardware grains for your minion.
  180 # enable_gpu_grains: True
  181 
  182 # Set the default outputter used by the salt-call command. The default is
  183 # "nested".
  184 #output: nested
  185 
  186 # To set a list of additional directories to search for salt outputters, set the
  187 # outputter_dirs option.
  188 #outputter_dirs: []
  189 
  190 # By default output is colored. To disable colored output, set the color value
  191 # to False.
  192 #color: True
  193 
  194 # Do not strip off the colored output from nested results and state outputs
  195 # (true by default).
  196 # strip_colors: False
  197 
  198 # Backup files that are replaced by file.managed and file.recurse under
  199 # 'cachedir'/file_backup relative to their original location and appended
  200 # with a timestamp. The only valid setting is "minion". Disabled by default.
  201 #
  202 # Alternatively this can be specified for each file in state files:
  203 # /etc/ssh/sshd_config:
  204 #   file.managed:
  205 #     - source: salt://ssh/sshd_config
  206 #     - backup: minion
  207 #
  208 #backup_mode: minion
  209 
  210 # When waiting for a master to accept the minion's public key, salt will
  211 # continuously attempt to reconnect until successful. This is the time, in
  212 # seconds, between those reconnection attempts.
  213 #acceptance_wait_time: 10
  214 
  215 # If this is nonzero, the time between reconnection attempts will increase by
  216 # acceptance_wait_time seconds per iteration, up to this maximum. If this is
  217 # set to zero, the time between reconnection attempts will stay constant.
  218 #acceptance_wait_time_max: 0
  219 
  220 # If the master rejects the minion's public key, retry instead of exiting.
  221 # Rejected keys will be handled the same as waiting on acceptance.
  222 #rejected_retry: False
  223 
  224 # When the master key changes, the minion will try to re-auth itself to receive
  225 # the new master key. In larger environments this can cause a SYN flood on the
  226 # master because all minions try to re-auth immediately. To prevent this and
  227 # have a minion wait for a random amount of time, use this optional parameter.
  228 # The wait-time will be a random number of seconds between 0 and the defined value.
  229 #random_reauth_delay: 60
  230 
  231 
  232 # To avoid overloading a master when many minions startup at once, a randomized
  233 # delay may be set to tell the minions to wait before connecting to the master.
  234 # This value is the number of seconds to choose from for a random number. For
  235 # example, setting this value to 60 will choose a random number of seconds to delay
  236 # on startup between zero seconds and sixty seconds. Setting to '0' will disable
  237 # this feature.
  238 #random_startup_delay: 0
  239 
  240 # When waiting for a master to accept the minion's public key, salt will
  241 # continuously attempt to reconnect until successful. This is the timeout value,
  242 # in seconds, for each individual attempt. After this timeout expires, the minion
  243 # will wait for acceptance_wait_time seconds before trying again. Unless your master
  244 # is under unusually heavy load, this should be left at the default.
  245 #auth_timeout: 60
  246 
  247 # Number of consecutive SaltReqTimeoutError that are acceptable when trying to
  248 # authenticate.
  249 #auth_tries: 7
  250 
  251 # The number of attempts to connect to a master before giving up.
  252 # Set this to -1 for unlimited attempts. This allows for a master to have
  253 # downtime and the minion to reconnect to it later when it comes back up.
  254 # In 'failover' mode, it is the number of attempts for each set of masters.
  255 # In this mode, it will cycle through the list of masters for each attempt.
  256 #
  257 # This is different than auth_tries because auth_tries attempts to
  258 # retry auth attempts with a single master. auth_tries is under the
  259 # assumption that you can connect to the master but not gain
  260 # authorization from it. master_tries will still cycle through all
  261 # the masters in a given try, so it is appropriate if you expect
  262 # occasional downtime from the master(s).
  263 #master_tries: 1
  264 
  265 # If authentication fails due to SaltReqTimeoutError during a ping_interval,
  266 # cause sub minion process to restart.
  267 #auth_safemode: False
  268 
  269 # Ping Master to ensure connection is alive (minutes).
  270 #ping_interval: 0
  271 
  272 # To auto recover minions if master changes IP address (DDNS)
  273 #    auth_tries: 10
  274 #    auth_safemode: False
  275 #    ping_interval: 2
  276 #
  277 # Minions won't know master is missing until a ping fails. After the ping fail,
  278 # the minion will attempt authentication and likely fails out and cause a restart.
  279 # When the minion restarts it will resolve the masters IP and attempt to reconnect.
  280 
  281 # If you don't have any problems with syn-floods, don't bother with the
  282 # three recon_* settings described below, just leave the defaults!
  283 #
  284 # The ZeroMQ pull-socket that binds to the masters publishing interface tries
  285 # to reconnect immediately, if the socket is disconnected (for example if
  286 # the master processes are restarted). In large setups this will have all
  287 # minions reconnect immediately which might flood the master (the ZeroMQ-default
  288 # is usually a 100ms delay). To prevent this, these three recon_* settings
  289 # can be used.
  290 # recon_default: the interval in milliseconds that the socket should wait before
  291 #                trying to reconnect to the master (1000ms = 1 second)
  292 #
  293 # recon_max: the maximum time a socket should wait. each interval the time to wait
  294 #            is calculated by doubling the previous time. if recon_max is reached,
  295 #            it starts again at recon_default. Short example:
  296 #
  297 #            reconnect 1: the socket will wait 'recon_default' milliseconds
  298 #            reconnect 2: 'recon_default' * 2
  299 #            reconnect 3: ('recon_default' * 2) * 2
  300 #            reconnect 4: value from previous interval * 2
  301 #            reconnect 5: value from previous interval * 2
  302 #            reconnect x: if value >= recon_max, it starts again with recon_default
  303 #
  304 # recon_randomize: generate a random wait time on minion start. The wait time will
  305 #                  be a random value between recon_default and recon_default +
  306 #                  recon_max. Having all minions reconnect with the same recon_default
  307 #                  and recon_max value kind of defeats the purpose of being able to
  308 #                  change these settings. If all minions have the same values and your
  309 #                  setup is quite large (several thousand minions), they will still
  310 #                  flood the master. The desired behavior is to have timeframe within
  311 #                  all minions try to reconnect.
  312 #
  313 # Example on how to use these settings. The goal: have all minions reconnect within a
  314 # 60 second timeframe on a disconnect.
  315 # recon_default: 1000
  316 # recon_max: 59000
  317 # recon_randomize: True
  318 #
  319 # Each minion will have a randomized reconnect value between 'recon_default'
  320 # and 'recon_default + recon_max', which in this example means between 1000ms
  321 # 60000ms (or between 1 and 60 seconds). The generated random-value will be
  322 # doubled after each attempt to reconnect. Lets say the generated random
  323 # value is 11 seconds (or 11000ms).
  324 # reconnect 1: wait 11 seconds
  325 # reconnect 2: wait 22 seconds
  326 # reconnect 3: wait 33 seconds
  327 # reconnect 4: wait 44 seconds
  328 # reconnect 5: wait 55 seconds
  329 # reconnect 6: wait time is bigger than 60 seconds (recon_default + recon_max)
  330 # reconnect 7: wait 11 seconds
  331 # reconnect 8: wait 22 seconds
  332 # reconnect 9: wait 33 seconds
  333 # reconnect x: etc.
  334 #
  335 # In a setup with ~6000 hosts these settings would average the reconnects
  336 # to about 100 per second and all hosts would be reconnected within 60 seconds.
  337 # recon_default: 100
  338 # recon_max: 5000
  339 # recon_randomize: False
  340 #
  341 #
  342 # The loop_interval sets how long in seconds the minion will wait between
  343 # evaluating the scheduler and running cleanup tasks.  This defaults to 1
  344 # second on the minion scheduler.
  345 #loop_interval: 1
  346 
  347 # Some installations choose to start all job returns in a cache or a returner
  348 # and forgo sending the results back to a master. In this workflow, jobs
  349 # are most often executed with --async from the Salt CLI and then results
  350 # are evaluated by examining job caches on the minions or any configured returners.
  351 # WARNING: Setting this to False will **disable** returns back to the master.
  352 #pub_ret: True
  353 
  354 
  355 # The grains can be merged, instead of overridden, using this option.
  356 # This allows custom grains to defined different subvalues of a dictionary
  357 # grain. By default this feature is disabled, to enable set grains_deep_merge
  358 # to ``True``.
  359 #grains_deep_merge: False
  360 
  361 # The grains_refresh_every setting allows for a minion to periodically check
  362 # its grains to see if they have changed and, if so, to inform the master
  363 # of the new grains. This operation is moderately expensive, therefore
  364 # care should be taken not to set this value too low.
  365 #
  366 # Note: This value is expressed in __minutes__!
  367 #
  368 # A value of 10 minutes is a reasonable default.
  369 #
  370 # If the value is set to zero, this check is disabled.
  371 #grains_refresh_every: 1
  372 
  373 # Cache grains on the minion. Default is False.
  374 #grains_cache: False
  375 
  376 # Cache rendered pillar data on the minion. Default is False.
  377 # This may cause 'cachedir'/pillar to contain sensitive data that should be
  378 # protected accordingly.
  379 #minion_pillar_cache: False
  380 
  381 # Grains cache expiration, in seconds. If the cache file is older than this
  382 # number of seconds then the grains cache will be dumped and fully re-populated
  383 # with fresh data. Defaults to 5 minutes. Will have no effect if 'grains_cache'
  384 # is not enabled.
  385 # grains_cache_expiration: 300
  386 
  387 # Determines whether or not the salt minion should run scheduled mine updates.
  388 # Defaults to "True". Set to "False" to disable the scheduled mine updates
  389 # (this essentially just does not add the mine update function to the minion's
  390 # scheduler).
  391 #mine_enabled: True
  392 
  393 # Determines whether or not scheduled mine updates should be accompanied by a job
  394 # return for the job cache. Defaults to "False". Set to "True" to include job
  395 # returns in the job cache for mine updates.
  396 #mine_return_job: False
  397 
  398 # Example functions that can be run via the mine facility
  399 # NO mine functions are established by default.
  400 # Note these can be defined in the minion's pillar as well.
  401 #mine_functions:
  402 #  test.ping: []
  403 #  network.ip_addrs:
  404 #    interface: eth0
  405 #    cidr: '10.0.0.0/8'
  406 
  407 # The number of minutes between mine updates.
  408 #mine_interval: 60
  409 
  410 # Windows platforms lack posix IPC and must rely on slower TCP based inter-
  411 # process communications.  ipc_mode is set to 'tcp' on such systems.
  412 #ipc_mode: ipc
  413 
  414 # Overwrite the default tcp ports used by the minion when ipc_mode is set to 'tcp'
  415 #tcp_pub_port: 4510
  416 #tcp_pull_port: 4511
  417 
  418 # Passing very large events can cause the minion to consume large amounts of
  419 # memory. This value tunes the maximum size of a message allowed onto the
  420 # minion event bus. The value is expressed in bytes.
  421 #max_event_size: 1048576
  422 
  423 # When a minion starts up it sends a notification on the event bus with a tag
  424 # that looks like this: `salt/minion/<minion_id>/start`. For historical reasons
  425 # the minion also sends a similar event with an event tag like this:
  426 # `minion_start`. This duplication can cause a lot of clutter on the event bus
  427 # when there are many minions. Set `enable_legacy_startup_events: False` in the
  428 # minion config to ensure only the `salt/minion/<minion_id>/start` events are
  429 # sent. Beginning with the `Sodium` Salt release this option will default to
  430 # `False`
  431 #enable_legacy_startup_events: True
  432 
  433 # To detect failed master(s) and fire events on connect/disconnect, set
  434 # master_alive_interval to the number of seconds to poll the masters for
  435 # connection events.
  436 #
  437 #master_alive_interval: 30
  438 
  439 # The minion can include configuration from other files. To enable this,
  440 # pass a list of paths to this option. The paths can be either relative or
  441 # absolute; if relative, they are considered to be relative to the directory
  442 # the main minion configuration file lives in (this file). Paths can make use
  443 # of shell-style globbing. If no files are matched by a path passed to this
  444 # option then the minion will log a warning message.
  445 #
  446 # Include a config file from some other path:
  447 # include: /etc/salt/extra_config
  448 #
  449 # Include config from several files and directories:
  450 #include:
  451 #  - /etc/salt/extra_config
  452 #  - /etc/roles/webserver
  453 
  454 # The syndic minion can verify that it is talking to the correct master via the
  455 # key fingerprint of the higher-level master with the "syndic_finger" config.
  456 #syndic_finger: ''
  457 #
  458 #
  459 #
  460 #####   Minion module management     #####
  461 ##########################################
  462 # Disable specific modules. This allows the admin to limit the level of
  463 # access the master has to the minion.  The default here is the empty list,
  464 # below is an example of how this needs to be formatted in the config file
  465 #disable_modules:
  466 #  - cmdmod
  467 #  - test
  468 #disable_returners: []
  469 
  470 # This is the reverse of disable_modules.  The default, like disable_modules, is the empty list,
  471 # but if this option is set to *anything* then *only* those modules will load.
  472 # Note that this is a very large hammer and it can be quite difficult to keep the minion working
  473 # the way you think it should since Salt uses many modules internally itself.  At a bare minimum
  474 # you need the following enabled or else the minion won't start.
  475 #whitelist_modules:
  476 #  - cmdmod
  477 #  - test
  478 #  - config
  479 
  480 # Modules can be loaded from arbitrary paths. This enables the easy deployment
  481 # of third party modules. Modules for returners and minions can be loaded.
  482 # Specify a list of extra directories to search for minion modules and
  483 # returners. These paths must be fully qualified!
  484 #module_dirs: []
  485 #returner_dirs: []
  486 #states_dirs: []
  487 #render_dirs: []
  488 #utils_dirs: []
  489 #
  490 # A module provider can be statically overwritten or extended for the minion
  491 # via the providers option, in this case the default module will be
  492 # overwritten by the specified module. In this example the pkg module will
  493 # be provided by the yumpkg5 module instead of the system default.
  494 #providers:
  495 #  pkg: yumpkg5
  496 #
  497 # Enable Cython modules searching and loading. (Default: False)
  498 #cython_enable: False
  499 #
  500 # Specify a max size (in bytes) for modules on import. This feature is currently
  501 # only supported on *nix operating systems and requires psutil.
  502 # modules_max_memory: -1
  503 
  504 
  505 #####    State Management Settings    #####
  506 ###########################################
  507 # The default renderer to use in SLS files. This is configured as a
  508 # pipe-delimited expression. For example, jinja|yaml will first run jinja
  509 # templating on the SLS file, and then load the result as YAML. This syntax is
  510 # documented in further depth at the following URL:
  511 #
  512 # https://docs.saltstack.com/en/latest/ref/renderers/#composing-renderers
  513 #
  514 # NOTE: The "shebang" prefix (e.g. "#!jinja|yaml") described in the
  515 # documentation linked above is for use in an SLS file to override the default
  516 # renderer, it should not be used when configuring the renderer here.
  517 #
  518 #renderer: jinja|yaml
  519 #
  520 # The failhard option tells the minions to stop immediately after the first
  521 # failure detected in the state execution. Defaults to False.
  522 #failhard: False
  523 #
  524 # Reload the modules prior to a highstate run.
  525 #autoload_dynamic_modules: True
  526 #
  527 # clean_dynamic_modules keeps the dynamic modules on the minion in sync with
  528 # the dynamic modules on the master, this means that if a dynamic module is
  529 # not on the master it will be deleted from the minion. By default, this is
  530 # enabled and can be disabled by changing this value to False.
  531 #clean_dynamic_modules: True
  532 #
  533 # Renamed from ``environment`` to ``saltenv``. If ``environment`` is used,
  534 # ``saltenv`` will take its value. If both are used, ``environment`` will be
  535 # ignored and ``saltenv`` will be used.
  536 # Normally the minion is not isolated to any single environment on the master
  537 # when running states, but the environment can be isolated on the minion side
  538 # by statically setting it. Remember that the recommended way to manage
  539 # environments is to isolate via the top file.
  540 #saltenv: None
  541 #
  542 # Isolates the pillar environment on the minion side. This functions the same
  543 # as the environment setting, but for pillar instead of states.
  544 #pillarenv: None
  545 #
  546 # Set this option to True to force the pillarenv to be the same as the
  547 # effective saltenv when running states. Note that if pillarenv is specified,
  548 # this option will be ignored.
  549 #pillarenv_from_saltenv: False
  550 #
  551 # Set this option to 'True' to force a 'KeyError' to be raised whenever an
  552 # attempt to retrieve a named value from pillar fails. When this option is set
  553 # to 'False', the failed attempt returns an empty string. Default is 'False'.
  554 #pillar_raise_on_missing: False
  555 #
  556 # If using the local file directory, then the state top file name needs to be
  557 # defined, by default this is top.sls.
  558 #state_top: top.sls
  559 #
  560 # Run states when the minion daemon starts. To enable, set startup_states to:
  561 # 'highstate' -- Execute state.highstate
  562 # 'sls' -- Read in the sls_list option and execute the named sls files
  563 # 'top' -- Read top_file option and execute based on that file on the Master
  564 #startup_states: ''
  565 #
  566 # List of states to run when the minion starts up if startup_states is 'sls':
  567 #sls_list:
  568 #  - edit.vim
  569 #  - hyper
  570 #
  571 # List of grains to pass in start event when minion starts up:
  572 #start_event_grains:
  573 #  - machine_id
  574 #  - uuid
  575 #
  576 # Top file to execute if startup_states is 'top':
  577 #top_file: ''
  578 
  579 # Automatically aggregate all states that have support for mod_aggregate by
  580 # setting to True. Or pass a list of state module names to automatically
  581 # aggregate just those types.
  582 #
  583 # state_aggregate:
  584 #   - pkg
  585 #
  586 #state_aggregate: False
  587 
  588 # Disable requisites during state runs by specifying a single requisite
  589 # or a list of requisites to disable.
  590 #
  591 # disabled_requisites: require_in
  592 #
  593 # disabled_requisites:
  594 #     - require
  595 #     - require_in
  596 
  597 #####     File Directory Settings    #####
  598 ##########################################
  599 # The Salt Minion can redirect all file server operations to a local directory,
  600 # this allows for the same state tree that is on the master to be used if
  601 # copied completely onto the minion. This is a literal copy of the settings on
  602 # the master but used to reference a local directory on the minion.
  603 
  604 # Set the file client. The client defaults to looking on the master server for
  605 # files, but can be directed to look at the local file directory setting
  606 # defined below by setting it to "local". Setting a local file_client runs the
  607 # minion in masterless mode.
  608 #file_client: remote
  609 
  610 # The file directory works on environments passed to the minion, each environment
  611 # can have multiple root directories, the subdirectories in the multiple file
  612 # roots cannot match, otherwise the downloaded files will not be able to be
  613 # reliably ensured. A base environment is required to house the top file.
  614 # Example:
  615 # file_roots:
  616 #   base:
  617 #     - /srv/salt/
  618 #   dev:
  619 #     - /srv/salt/dev/services
  620 #     - /srv/salt/dev/states
  621 #   prod:
  622 #     - /srv/salt/prod/services
  623 #     - /srv/salt/prod/states
  624 #
  625 #file_roots:
  626 #  base:
  627 #    - /srv/salt
  628 
  629 # Uncomment the line below if you do not want the file_server to follow
  630 # symlinks when walking the filesystem tree. This is set to True
  631 # by default. Currently this only applies to the default roots
  632 # fileserver_backend.
  633 #fileserver_followsymlinks: False
  634 #
  635 # Uncomment the line below if you do not want symlinks to be
  636 # treated as the files they are pointing to. By default this is set to
  637 # False. By uncommenting the line below, any detected symlink while listing
  638 # files on the Master will not be returned to the Minion.
  639 #fileserver_ignoresymlinks: True
  640 #
  641 # By default, the Salt fileserver recurses fully into all defined environments
  642 # to attempt to find files. To limit this behavior so that the fileserver only
  643 # traverses directories with SLS files and special Salt directories like _modules,
  644 # enable the option below. This might be useful for installations where a file root
  645 # has a very large number of files and performance is negatively impacted. Default
  646 # is False.
  647 #fileserver_limit_traversal: False
  648 
  649 # The hash_type is the hash to use when discovering the hash of a file on
  650 # the local fileserver. The default is sha256, but md5, sha1, sha224, sha384
  651 # and sha512 are also supported.
  652 #
  653 # WARNING: While md5 and sha1 are also supported, do not use them due to the
  654 # high chance of possible collisions and thus security breach.
  655 #
  656 # Warning: Prior to changing this value, the minion should be stopped and all
  657 # Salt caches should be cleared.
  658 #hash_type: sha256
  659 
  660 # The Salt pillar is searched for locally if file_client is set to local. If
  661 # this is the case, and pillar data is defined, then the pillar_roots need to
  662 # also be configured on the minion:
  663 #pillar_roots:
  664 #  base:
  665 #    - /srv/pillar
  666 
  667 # Set a hard-limit on the size of the files that can be pushed to the master.
  668 # It will be interpreted as megabytes. Default: 100
  669 #file_recv_max_size: 100
  670 #
  671 #
  672 ######        Security settings       #####
  673 ###########################################
  674 # Enable "open mode", this mode still maintains encryption, but turns off
  675 # authentication, this is only intended for highly secure environments or for
  676 # the situation where your keys end up in a bad state. If you run in open mode
  677 # you do so at your own risk!
  678 #open_mode: False
  679 
  680 # The size of key that should be generated when creating new keys.
  681 #keysize: 2048
  682 
  683 # Enable permissive access to the salt keys.  This allows you to run the
  684 # master or minion as root, but have a non-root group be given access to
  685 # your pki_dir.  To make the access explicit, root must belong to the group
  686 # you've given access to. This is potentially quite insecure.
  687 #permissive_pki_access: False
  688 
  689 # The state_verbose and state_output settings can be used to change the way
  690 # state system data is printed to the display. By default all data is printed.
  691 # The state_verbose setting can be set to True or False, when set to False
  692 # all data that has a result of True and no changes will be suppressed.
  693 #state_verbose: True
  694 
  695 # The state_output setting controls which results will be output full multi line
  696 # full, terse - each state will be full/terse
  697 # mixed - only states with errors will be full
  698 # changes - states with changes and errors will be full
  699 # full_id, mixed_id, changes_id and terse_id are also allowed;
  700 # when set, the state ID will be used as name in the output
  701 #state_output: full
  702 
  703 # The state_output_diff setting changes whether or not the output from
  704 # successful states is returned. Useful when even the terse output of these
  705 # states is cluttering the logs. Set it to True to ignore them.
  706 #state_output_diff: False
  707 
  708 # The state_output_profile setting changes whether profile information
  709 # will be shown for each state run.
  710 #state_output_profile: True
  711 
  712 # Fingerprint of the master public key to validate the identity of your Salt master
  713 # before the initial key exchange. The master fingerprint can be found by running
  714 # "salt-key -f master.pub" on the Salt master.
  715 #master_finger: ''
  716 
  717 # Use TLS/SSL encrypted connection between master and minion.
  718 # Can be set to a dictionary containing keyword arguments corresponding to Python's
  719 # 'ssl.wrap_socket' method.
  720 # Default is None.
  721 #ssl:
  722 #    keyfile: <path_to_keyfile>
  723 #    certfile: <path_to_certfile>
  724 #    ssl_version: PROTOCOL_TLSv1_2
  725 
  726 # Grains to be sent to the master on authentication to check if the minion's key
  727 # will be accepted automatically. Needs to be configured on the master.
  728 #autosign_grains:
  729 #  - uuid
  730 #  - server_id
  731 
  732 
  733 ######        Reactor Settings        #####
  734 ###########################################
  735 # Define a salt reactor. See https://docs.saltstack.com/en/latest/topics/reactor/
  736 #reactor: []
  737 
  738 #Set the TTL for the cache of the reactor configuration.
  739 #reactor_refresh_interval: 60
  740 
  741 #Configure the number of workers for the runner/wheel in the reactor.
  742 #reactor_worker_threads: 10
  743 
  744 #Define the queue size for workers in the reactor.
  745 #reactor_worker_hwm: 10000
  746 
  747 
  748 ######         Thread settings        #####
  749 ###########################################
  750 # Disable multiprocessing support, by default when a minion receives a
  751 # publication a new process is spawned and the command is executed therein.
  752 #
  753 # WARNING: Disabling multiprocessing may result in substantial slowdowns
  754 # when processing large pillars. See https://github.com/saltstack/salt/issues/38758
  755 # for a full explanation.
  756 #multiprocessing: True
  757 
  758 # Limit the maximum amount of processes or threads created by salt-minion.
  759 # This is useful to avoid resource exhaustion in case the minion receives more
  760 # publications than it is able to handle, as it limits the number of spawned
  761 # processes or threads. -1 is the default and disables the limit.
  762 #process_count_max: -1
  763 
  764 
  765 #####         Logging settings       #####
  766 ##########################################
  767 # The location of the minion log file
  768 # The minion log can be sent to a regular file, local path name, or network
  769 # location. Remote logging works best when configured to use rsyslogd(8) (e.g.:
  770 # ``file:///dev/log``), with rsyslogd(8) configured for network logging. The URI
  771 # format is: <file|udp|tcp>://<host|socketpath>:<port-if-required>/<log-facility>
  772 #log_file: /var/log/salt/minion
  773 #log_file: file:///dev/log
  774 #log_file: udp://loghost:10514
  775 #
  776 #log_file: /var/log/salt/minion
  777 #key_logfile: /var/log/salt/key
  778 
  779 # The level of messages to send to the console.
  780 # One of 'garbage', 'trace', 'debug', 'info', 'warning', 'error', 'critical'.
  781 #
  782 # The following log levels are considered INSECURE and may log sensitive data:
  783 # ['garbage', 'trace', 'debug']
  784 #
  785 # Default: 'warning'
  786 #log_level: warning
  787 
  788 # The level of messages to send to the log file.
  789 # One of 'garbage', 'trace', 'debug', info', 'warning', 'error', 'critical'.
  790 # If using 'log_granular_levels' this must be set to the highest desired level.
  791 # Default: 'warning'
  792 #log_level_logfile:
  793 
  794 # The date and time format used in log messages. Allowed date/time formatting
  795 # can be seen here: http://docs.python.org/library/time.html#time.strftime
  796 #log_datefmt: '%H:%M:%S'
  797 #log_datefmt_logfile: '%Y-%m-%d %H:%M:%S'
  798 
  799 # The format of the console logging messages. Allowed formatting options can
  800 # be seen here: http://docs.python.org/library/logging.html#logrecord-attributes
  801 #
  802 # Console log colors are specified by these additional formatters:
  803 #
  804 # %(colorlevel)s
  805 # %(colorname)s
  806 # %(colorprocess)s
  807 # %(colormsg)s
  808 #
  809 # Since it is desirable to include the surrounding brackets, '[' and ']', in
  810 # the coloring of the messages, these color formatters also include padding as
  811 # well.  Color LogRecord attributes are only available for console logging.
  812 #
  813 #log_fmt_console: '%(colorlevel)s %(colormsg)s'
  814 #log_fmt_console: '[%(levelname)-8s] %(message)s'
  815 #
  816 #log_fmt_logfile: '%(asctime)s,%(msecs)03d [%(name)-17s][%(levelname)-8s] %(message)s'
  817 
  818 # This can be used to control logging levels more specificically.  This
  819 # example sets the main salt library at the 'warning' level, but sets
  820 # 'salt.modules' to log at the 'debug' level:
  821 #   log_granular_levels:
  822 #     'salt': 'warning'
  823 #     'salt.modules': 'debug'
  824 #
  825 #log_granular_levels: {}
  826 
  827 # To diagnose issues with minions disconnecting or missing returns, ZeroMQ
  828 # supports the use of monitor sockets to log connection events. This
  829 # feature requires ZeroMQ 4.0 or higher.
  830 #
  831 # To enable ZeroMQ monitor sockets, set 'zmq_monitor' to 'True' and log at a
  832 # debug level or higher.
  833 #
  834 # A sample log event is as follows:
  835 #
  836 # [DEBUG   ] ZeroMQ event: {'endpoint': 'tcp://127.0.0.1:4505', 'event': 512,
  837 # 'value': 27, 'description': 'EVENT_DISCONNECTED'}
  838 #
  839 # All events logged will include the string 'ZeroMQ event'. A connection event
  840 # should be logged as the minion starts up and initially connects to the
  841 # master. If not, check for debug log level and that the necessary version of
  842 # ZeroMQ is installed.
  843 #
  844 #zmq_monitor: False
  845 
  846 # Number of times to try to authenticate with the salt master when reconnecting
  847 # to the master
  848 #tcp_authentication_retries: 5
  849 
  850 ######      Module configuration      #####
  851 ###########################################
  852 # Salt allows for modules to be passed arbitrary configuration data, any data
  853 # passed here in valid yaml format will be passed on to the salt minion modules
  854 # for use. It is STRONGLY recommended that a naming convention be used in which
  855 # the module name is followed by a . and then the value. Also, all top level
  856 # data must be applied via the yaml dict construct, some examples:
  857 #
  858 # You can specify that all modules should run in test mode:
  859 #test: True
  860 #
  861 # A simple value for the test module:
  862 #test.foo: foo
  863 #
  864 # A list for the test module:
  865 #test.bar: [baz,quo]
  866 #
  867 # A dict for the test module:
  868 #test.baz: {spam: sausage, cheese: bread}
  869 #
  870 #
  871 ######      Update settings          ######
  872 ###########################################
  873 # Using the features in Esky, a salt minion can both run as a frozen app and
  874 # be updated on the fly. These options control how the update process
  875 # (saltutil.update()) behaves.
  876 #
  877 # The url for finding and downloading updates. Disabled by default.
  878 #update_url: False
  879 #
  880 # The list of services to restart after a successful update. Empty by default.
  881 #update_restart_services: []
  882 
  883 
  884 ######      Keepalive settings        ######
  885 ############################################
  886 # ZeroMQ now includes support for configuring SO_KEEPALIVE if supported by
  887 # the OS. If connections between the minion and the master pass through
  888 # a state tracking device such as a firewall or VPN gateway, there is
  889 # the risk that it could tear down the connection the master and minion
  890 # without informing either party that their connection has been taken away.
  891 # Enabling TCP Keepalives prevents this from happening.
  892 
  893 # Overall state of TCP Keepalives, enable (1 or True), disable (0 or False)
  894 # or leave to the OS defaults (-1), on Linux, typically disabled. Default True, enabled.
  895 #tcp_keepalive: True
  896 
  897 # How long before the first keepalive should be sent in seconds. Default 300
  898 # to send the first keepalive after 5 minutes, OS default (-1) is typically 7200 seconds
  899 # on Linux see /proc/sys/net/ipv4/tcp_keepalive_time.
  900 #tcp_keepalive_idle: 300
  901 
  902 # How many lost probes are needed to consider the connection lost. Default -1
  903 # to use OS defaults, typically 9 on Linux, see /proc/sys/net/ipv4/tcp_keepalive_probes.
  904 #tcp_keepalive_cnt: -1
  905 
  906 # How often, in seconds, to send keepalives after the first one. Default -1 to
  907 # use OS defaults, typically 75 seconds on Linux, see
  908 # /proc/sys/net/ipv4/tcp_keepalive_intvl.
  909 #tcp_keepalive_intvl: -1
  910 
  911 
  912 ######   Windows Software settings    ######
  913 ############################################
  914 # Location of the repository cache file on the master:
  915 #win_repo_cachefile: 'salt://win/repo/winrepo.p'
  916 
  917 
  918 ######      Returner  settings        ######
  919 ############################################
  920 # Default Minion returners. Can be a comma delimited string or a list:
  921 #
  922 #return: mysql
  923 #
  924 #return: mysql,slack,redis
  925 #
  926 #return:
  927 #  - mysql
  928 #  - hipchat
  929 #  - slack
  930 
  931 
  932 ######    Miscellaneous  settings     ######
  933 ############################################
  934 # Default match type for filtering events tags: startswith, endswith, find, regex, fnmatch
  935 #event_match_type: startswith