|
2 | 2 | ##### Primary configuration settings ##### |
3 | 3 | ########################################## |
4 | 4 | # Set the location of the salt master server, if the master server cannot be |
5 | | -# resolved, then the minion will fail to start |
| 5 | +# resolved, then the minion will fail to start. |
6 | 6 | #master: salt |
7 | 7 |
|
8 | | -# Set the post used by the master reply and authentication server |
| 8 | +# Set the port used by the master reply and authentication server |
9 | 9 | #master_port: 4506 |
10 | 10 |
|
11 | 11 | # The user to run salt |
|
24 | 24 | # clusters. |
25 | 25 | #id: |
26 | 26 |
|
27 | | -# The minion connection to the master may be inturupted, the minion will |
28 | | -# verify the connection every so many seconds, to disable connection |
29 | | -# verification set this value to 0 |
| 27 | +# If the the connection to the server is interrupted, the minion will |
| 28 | +# attempt to reconnect. sub_timeout allows you to control the rate |
| 29 | +# of reconnection attempts (in seconds). To disable reconnects, set |
| 30 | +# this value to 0. |
30 | 31 | #sub_timeout: 60 |
31 | 32 |
|
32 | 33 | # Where cache data goes |
33 | 34 | #cachedir: /var/cache/salt |
34 | 35 |
|
35 | 36 | # The minion can locally cache the return data from jobs sent to it, this |
36 | | -# can be a good way to keep track minion side of the jobs the minion has |
37 | | -# executed. By default this feature is disabled, to enable set cache_jobs |
38 | | -# to True |
| 37 | +# can be a good way to keep track of jobs the minion has executed |
| 38 | +# (on the minion side). By default this feature is disabled, to enable |
| 39 | +# set cache_jobs to True |
39 | 40 | #cache_jobs: False |
40 | 41 |
|
41 | 42 | # When waiting for a master to accept the minion's public key, salt will |
|
47 | 48 |
|
48 | 49 | ##### Minion module management ##### |
49 | 50 | ########################################## |
50 | | -# Disable specific modules, this will allow the admin to limit the level os |
| 51 | +# Disable specific modules. This allows the admin to limit the level of |
51 | 52 | # access the master has to the minion |
52 | 53 | #disable_modules: [cmd,test] |
53 | 54 | #disable_returners: [] |
54 | | -# Modules can be loaded from arbitrary paths, this enables the easy deployment |
55 | | -# of third party modules, modules for returners and minions can be loaded. |
| 55 | +# |
| 56 | +# Modules can be loaded from arbitrary paths. This enables the easy deployment |
| 57 | +# of third party modules. Modules for returners and minions can be loaded. |
56 | 58 | # Specify a list of extra directories to search for minion modules and |
57 | 59 | # returners. These paths must be fully qualified! |
58 | 60 | #module_dirs: [] |
59 | 61 | #returner_dirs: [] |
60 | 62 | #states_dirs: [] |
61 | 63 | #render_dirs: [] |
| 64 | +# |
62 | 65 | # Enable Cython modules searching and loading. (Default: False) |
63 | 66 | #cython_enable: False |
64 | 67 |
|
|
92 | 95 | # not on the master it will be deleted from the minion. By default this is |
93 | 96 | # enabled and can be disabled by changing this value to False |
94 | 97 | #clean_dynamic_modules: True |
| 98 | +# |
| 99 | +# Normally the minion is not isolated to any single environment on the master |
| 100 | +# when running states, but the environment can be isolated on the minion side |
| 101 | +# by statically setting it. Remember that the recommended way to manage |
| 102 | +# environments is to issolate via the top file. |
| 103 | +#environment: None |
95 | 104 |
|
96 | 105 | ###### Security settings ##### |
97 | 106 | ########################################### |
|
112 | 121 | ########################################### |
113 | 122 | # The location of the minion log file |
114 | 123 | #log_file: /var/log/salt/minion |
| 124 | +# |
115 | 125 | # The level of messages to send to the log file. |
116 | 126 | # One of 'info', 'quiet', 'critical', 'error', 'debug', 'warning'. |
117 | 127 | # Default: 'warning' |
118 | 128 | #log_level: warning |
119 | 129 | # |
120 | 130 | # Logger levels can be used to tweak specific loggers logging levels. |
121 | | -# Imagine you want to have the salt library at the 'warning' level, but, you |
122 | | -# still wish to have 'salt.modules' at the 'debug' level: |
| 131 | +# For example, if you want to have the salt library at the 'warning' level, |
| 132 | +# but you still wish to have 'salt.modules' at the 'debug' level: |
123 | 133 | # log_granular_levels: { |
124 | 134 | # 'salt': 'warning', |
125 | 135 | # 'salt.modules': 'debug' |
|
133 | 143 | # passed here in valid yaml format will be passed on to the salt minion modules |
134 | 144 | # for use. It is STRONGLY recommended that a naming convention be used in which |
135 | 145 | # the module name is followed by a . and then the value. Also, all top level |
136 | | -# data must be allied via the yaml dict construct, some examples: |
| 146 | +# data must be applied via the yaml dict construct, some examples: |
137 | 147 | # |
138 | 148 | # A simple value for the test module: |
139 | 149 | #test.foo: foo |
|
0 commit comments