diff options
author | Alejandro del Castillo <alejandro.delcastillo@ni.com> | 2015-05-08 10:28:40 -0500 |
---|---|---|
committer | Bruce Ashfield <bruce.ashfield@windriver.com> | 2015-05-13 10:02:11 -0400 |
commit | 37644a8fe105425099c7c8c57b161720766105d5 (patch) | |
tree | 81c00baf1dd2dc91c142d7283ccfc70235d4d766 /meta-openstack/recipes-support/salt/files/master | |
parent | dd04ca6db2993404284679ea04a80d9071f90c2b (diff) | |
download | meta-cloud-services-37644a8fe105425099c7c8c57b161720766105d5.tar.gz |
salt: add recipe for salt
Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'meta-openstack/recipes-support/salt/files/master')
-rw-r--r-- | meta-openstack/recipes-support/salt/files/master | 525 |
1 files changed, 525 insertions, 0 deletions
diff --git a/meta-openstack/recipes-support/salt/files/master b/meta-openstack/recipes-support/salt/files/master new file mode 100644 index 0000000..8129a4f --- /dev/null +++ b/meta-openstack/recipes-support/salt/files/master | |||
@@ -0,0 +1,525 @@ | |||
1 | ##### Primary configuration settings ##### | ||
2 | ########################################## | ||
3 | # This configuration file is used to manage the behavior of the Salt Master | ||
4 | # Values that are commented out but have no space after the comment are | ||
5 | # defaults that need not be set in the config. If there is a space after the | ||
6 | # comment that the value is presented as an example and is not the default. | ||
7 | |||
8 | # Per default, the master will automatically include all config files | ||
9 | # from master.d/*.conf (master.d is a directory in the same directory | ||
10 | # as the main master config file) | ||
11 | #default_include: master.d/*.conf | ||
12 | |||
13 | # The address of the interface to bind to | ||
14 | #interface: 0.0.0.0 | ||
15 | |||
16 | # Whether the master should listen for IPv6 connections. If this is set to True, | ||
17 | # the interface option must be adjusted too (for example: "interface: '::'") | ||
18 | #ipv6: False | ||
19 | |||
20 | # The tcp port used by the publisher | ||
21 | #publish_port: 4505 | ||
22 | |||
23 | # The user to run the salt-master as. Salt will update all permissions to | ||
24 | # allow the specified user to run the master. If the modified files cause | ||
25 | # conflicts set verify_env to False. | ||
26 | #user: root | ||
27 | |||
28 | # Max open files | ||
29 | # Each minion connecting to the master uses AT LEAST one file descriptor, the | ||
30 | # master subscription connection. If enough minions connect you might start | ||
31 | # seeing on the console(and then salt-master crashes): | ||
32 | # Too many open files (tcp_listener.cpp:335) | ||
33 | # Aborted (core dumped) | ||
34 | # | ||
35 | # By default this value will be the one of `ulimit -Hn`, ie, the hard limit for | ||
36 | # max open files. | ||
37 | # | ||
38 | # If you wish to set a different value than the default one, uncomment and | ||
39 | # configure this setting. Remember that this value CANNOT be higher than the | ||
40 | # hard limit. Raising the hard limit depends on your OS and/or distribution, | ||
41 | # a good way to find the limit is to search the internet for(for example): | ||
42 | # raise max open files hard limit debian | ||
43 | # | ||
44 | #max_open_files: 100000 | ||
45 | |||
46 | # The number of worker threads to start, these threads are used to manage | ||
47 | # return calls made from minions to the master, if the master seems to be | ||
48 | # running slowly, increase the number of threads | ||
49 | #worker_threads: 5 | ||
50 | |||
51 | # The port used by the communication interface. The ret (return) port is the | ||
52 | # interface used for the file server, authentication, job returnes, etc. | ||
53 | #ret_port: 4506 | ||
54 | |||
55 | # Specify the location of the daemon process ID file | ||
56 | #pidfile: /var/run/salt-master.pid | ||
57 | |||
58 | # The root directory prepended to these options: pki_dir, cachedir, | ||
59 | # sock_dir, log_file, autosign_file, extension_modules, key_logfile, pidfile. | ||
60 | #root_dir: / | ||
61 | |||
62 | # Directory used to store public key data | ||
63 | #pki_dir: /etc/salt/pki/master | ||
64 | |||
65 | # Directory to store job and cache data | ||
66 | #cachedir: /var/cache/salt/master | ||
67 | |||
68 | # Verify and set permissions on configuration directories at startup | ||
69 | #verify_env: True | ||
70 | |||
71 | # Set the number of hours to keep old job information in the job cache | ||
72 | #keep_jobs: 24 | ||
73 | |||
74 | # Set the default timeout for the salt command and api, the default is 5 | ||
75 | # seconds | ||
76 | #timeout: 5 | ||
77 | |||
78 | # The loop_interval option controls the seconds for the master's maintinance | ||
79 | # process check cycle. This process updates file server backends, cleans the | ||
80 | # job cache and executes the scheduler. | ||
81 | #loop_interval: 60 | ||
82 | |||
83 | # Set the default outputter used by the salt command. The default is "nested" | ||
84 | #output: nested | ||
85 | |||
86 | # By default output is colored, to disable colored output set the color value | ||
87 | # to False | ||
88 | #color: True | ||
89 | |||
90 | # Set the directory used to hold unix sockets | ||
91 | #sock_dir: /var/run/salt/master | ||
92 | |||
93 | # The master can take a while to start up when lspci and/or dmidecode is used | ||
94 | # to populate the grains for the master. Enable if you want to see GPU hardware | ||
95 | # data for your master. | ||
96 | # | ||
97 | # enable_gpu_grains: False | ||
98 | |||
99 | # The master maintains a job cache, while this is a great addition it can be | ||
100 | # a burden on the master for larger deployments (over 5000 minions). | ||
101 | # Disabling the job cache will make previously executed jobs unavailable to | ||
102 | # the jobs system and is not generally recommended. | ||
103 | # | ||
104 | #job_cache: True | ||
105 | |||
106 | # Cache minion grains and pillar data in the cachedir. | ||
107 | #minion_data_cache: True | ||
108 | |||
109 | # The master can include configuration from other files. To enable this, | ||
110 | # pass a list of paths to this option. The paths can be either relative or | ||
111 | # absolute; if relative, they are considered to be relative to the directory | ||
112 | # the main master configuration file lives in (this file). Paths can make use | ||
113 | # of shell-style globbing. If no files are matched by a path passed to this | ||
114 | # option then the master will log a warning message. | ||
115 | # | ||
116 | # | ||
117 | # Include a config file from some other path: | ||
118 | #include: /etc/salt/extra_config | ||
119 | # | ||
120 | # Include config from several files and directories: | ||
121 | #include: | ||
122 | # - /etc/salt/extra_config | ||
123 | |||
124 | |||
125 | ##### Security settings ##### | ||
126 | ########################################## | ||
127 | # Enable "open mode", this mode still maintains encryption, but turns off | ||
128 | # authentication, this is only intended for highly secure environments or for | ||
129 | # the situation where your keys end up in a bad state. If you run in open mode | ||
130 | # you do so at your own risk! | ||
131 | #open_mode: False | ||
132 | |||
133 | # Enable auto_accept, this setting will automatically accept all incoming | ||
134 | # public keys from the minions. Note that this is insecure. | ||
135 | #auto_accept: False | ||
136 | |||
137 | # If the autosign_file is specified only incoming keys specified in | ||
138 | # the autosign_file will be automatically accepted. This is insecure. | ||
139 | # Regular expressions as well as globing lines are supported. | ||
140 | #autosign_file: /etc/salt/autosign.conf | ||
141 | |||
142 | # Enable permissive access to the salt keys. This allows you to run the | ||
143 | # master or minion as root, but have a non-root group be given access to | ||
144 | # your pki_dir. To make the access explicit, root must belong to the group | ||
145 | # you've given access to. This is potentially quite insecure. | ||
146 | # If an autosign_file is specified, enabling permissive_pki_access will allow group access | ||
147 | # to that specific file. | ||
148 | #permissive_pki_access: False | ||
149 | |||
150 | # Allow users on the master access to execute specific commands on minions. | ||
151 | # This setting should be treated with care since it opens up execution | ||
152 | # capabilities to non root users. By default this capability is completely | ||
153 | # disabled. | ||
154 | # | ||
155 | #client_acl: | ||
156 | # larry: | ||
157 | # - test.ping | ||
158 | # - network.* | ||
159 | # | ||
160 | |||
161 | # Blacklist any of the following users or modules | ||
162 | # | ||
163 | # This example would blacklist all non sudo users, including root from | ||
164 | # running any commands. It would also blacklist any use of the "cmd" | ||
165 | # module. | ||
166 | # This is completely disabled by default. | ||
167 | # | ||
168 | #client_acl_blacklist: | ||
169 | # users: | ||
170 | # - root | ||
171 | # - '^(?!sudo_).*$' # all non sudo users | ||
172 | # modules: | ||
173 | # - cmd | ||
174 | |||
175 | # The external auth system uses the Salt auth modules to authenticate and | ||
176 | # validate users to access areas of the Salt system. | ||
177 | # | ||
178 | #external_auth: | ||
179 | # pam: | ||
180 | # fred: | ||
181 | # - test.* | ||
182 | # | ||
183 | |||
184 | # Time (in seconds) for a newly generated token to live. Default: 12 hours | ||
185 | #token_expire: 43200 | ||
186 | |||
187 | # Allow minions to push files to the master. This is disabled by default, for | ||
188 | # security purposes. | ||
189 | #file_recv: False | ||
190 | |||
191 | # Signature verification on messages published from the master. | ||
192 | # This causes the master to cryptographically sign all messages published to its event | ||
193 | # bus, and minions then verify that signature before acting on the message. | ||
194 | # | ||
195 | # This is False by default. | ||
196 | # | ||
197 | # Note that to facilitate interoperability with masters and minions that are different | ||
198 | # versions, if sign_pub_messages is True but a message is received by a minion with | ||
199 | # no signature, it will still be accepted, and a warning message will be logged. | ||
200 | # Conversely, if sign_pub_messages is False, but a minion receives a signed | ||
201 | # message it will be accepted, the signature will not be checked, and a warning message | ||
202 | # will be logged. This behavior will go away in Salt 0.17.6 (or Hydrogen RC1, whichever | ||
203 | # comes first) and these two situations will cause minion to throw an exception and | ||
204 | # drop the message. | ||
205 | # | ||
206 | # sign_pub_messages: False | ||
207 | |||
208 | ##### Master Module Management ##### | ||
209 | ########################################## | ||
210 | # Manage how master side modules are loaded | ||
211 | |||
212 | # Add any additional locations to look for master runners | ||
213 | #runner_dirs: [] | ||
214 | |||
215 | # Enable Cython for master side modules | ||
216 | #cython_enable: False | ||
217 | |||
218 | |||
219 | ##### State System settings ##### | ||
220 | ########################################## | ||
221 | # The state system uses a "top" file to tell the minions what environment to | ||
222 | # use and what modules to use. The state_top file is defined relative to the | ||
223 | # root of the base environment as defined in "File Server settings" below. | ||
224 | #state_top: top.sls | ||
225 | |||
226 | # The master_tops option replaces the external_nodes option by creating | ||
227 | # a plugable system for the generation of external top data. The external_nodes | ||
228 | # option is deprecated by the master_tops option. | ||
229 | # To gain the capabilities of the classic external_nodes system, use the | ||
230 | # following configuration: | ||
231 | # master_tops: | ||
232 | # ext_nodes: <Shell command which returns yaml> | ||
233 | # | ||
234 | #master_tops: {} | ||
235 | |||
236 | # The external_nodes option allows Salt to gather data that would normally be | ||
237 | # placed in a top file. The external_nodes option is the executable that will | ||
238 | # return the ENC data. Remember that Salt will look for external nodes AND top | ||
239 | # files and combine the results if both are enabled! | ||
240 | #external_nodes: None | ||
241 | |||
242 | # The renderer to use on the minions to render the state data | ||
243 | #renderer: yaml_jinja | ||
244 | |||
245 | # The failhard option tells the minions to stop immediately after the first | ||
246 | # failure detected in the state execution, defaults to False | ||
247 | #failhard: False | ||
248 | |||
249 | # The state_verbose and state_output settings can be used to change the way | ||
250 | # state system data is printed to the display. By default all data is printed. | ||
251 | # The state_verbose setting can be set to True or False, when set to False | ||
252 | # all data that has a result of True and no changes will be suppressed. | ||
253 | #state_verbose: True | ||
254 | |||
255 | # The state_output setting changes if the output is the full multi line | ||
256 | # output for each changed state if set to 'full', but if set to 'terse' | ||
257 | # the output will be shortened to a single line. If set to 'mixed', the output | ||
258 | # will be terse unless a state failed, in which case that output will be full. | ||
259 | #state_output: full | ||
260 | |||
261 | |||
262 | ##### File Server settings ##### | ||
263 | ########################################## | ||
264 | # Salt runs a lightweight file server written in zeromq to deliver files to | ||
265 | # minions. This file server is built into the master daemon and does not | ||
266 | # require a dedicated port. | ||
267 | |||
268 | # The file server works on environments passed to the master, each environment | ||
269 | # can have multiple root directories, the subdirectories in the multiple file | ||
270 | # roots cannot match, otherwise the downloaded files will not be able to be | ||
271 | # reliably ensured. A base environment is required to house the top file. | ||
272 | # Example: | ||
273 | # file_roots: | ||
274 | # base: | ||
275 | # - /srv/salt/ | ||
276 | # dev: | ||
277 | # - /srv/salt/dev/services | ||
278 | # - /srv/salt/dev/states | ||
279 | # prod: | ||
280 | # - /srv/salt/prod/services | ||
281 | # - /srv/salt/prod/states | ||
282 | |||
283 | #file_roots: | ||
284 | # base: | ||
285 | # - /srv/salt | ||
286 | |||
287 | # The hash_type is the hash to use when discovering the hash of a file on | ||
288 | # the master server. The default is md5, but sha1, sha224, sha256, sha384 | ||
289 | # and sha512 are also supported. | ||
290 | #hash_type: md5 | ||
291 | |||
292 | # The buffer size in the file server can be adjusted here: | ||
293 | #file_buffer_size: 1048576 | ||
294 | |||
295 | # A regular expression (or a list of expressions) that will be matched | ||
296 | # against the file path before syncing the modules and states to the minions. | ||
297 | # This includes files affected by the file.recurse state. | ||
298 | # For example, if you manage your custom modules and states in subversion | ||
299 | # and don't want all the '.svn' folders and content synced to your minions, | ||
300 | # you could set this to '/\.svn($|/)'. By default nothing is ignored. | ||
301 | # | ||
302 | #file_ignore_regex: | ||
303 | # - '/\.svn($|/)' | ||
304 | # - '/\.git($|/)' | ||
305 | |||
306 | # A file glob (or list of file globs) that will be matched against the file | ||
307 | # path before syncing the modules and states to the minions. This is similar | ||
308 | # to file_ignore_regex above, but works on globs instead of regex. By default | ||
309 | # nothing is ignored. | ||
310 | # | ||
311 | # file_ignore_glob: | ||
312 | # - '*.pyc' | ||
313 | # - '*/somefolder/*.bak' | ||
314 | # - '*.swp' | ||
315 | |||
316 | # File Server Backend | ||
317 | # Salt supports a modular fileserver backend system, this system allows | ||
318 | # the salt master to link directly to third party systems to gather and | ||
319 | # manage the files available to minions. Multiple backends can be | ||
320 | # configured and will be searched for the requested file in the order in which | ||
321 | # they are defined here. The default setting only enables the standard backend | ||
322 | # "roots" which uses the "file_roots" option. | ||
323 | # | ||
324 | #fileserver_backend: | ||
325 | # - roots | ||
326 | # | ||
327 | # To use multiple backends list them in the order they are searched: | ||
328 | # | ||
329 | #fileserver_backend: | ||
330 | # - git | ||
331 | # - roots | ||
332 | # | ||
333 | # By default, the Salt fileserver recurses fully into all defined environments | ||
334 | # to attempt to find files. To limit this behavior so that the fileserver only | ||
335 | # traverses directories with SLS files and special Salt directories like _modules, | ||
336 | # enable the option below. This might be useful for installations where a file root | ||
337 | # has a very large number of files and performance is impacted. Default is False. | ||
338 | # | ||
339 | # fileserver_limit_traversal: False | ||
340 | # | ||
341 | # Git fileserver backend configuration | ||
342 | # When using the git fileserver backend at least one git remote needs to be | ||
343 | # defined. The user running the salt master will need read access to the repo. | ||
344 | # | ||
345 | #gitfs_remotes: | ||
346 | # - git://github.com/saltstack/salt-states.git | ||
347 | # - file:///var/git/saltmaster | ||
348 | # | ||
349 | # The repos will be searched in order to find the file requested by a client | ||
350 | # and the first repo to have the file will return it. | ||
351 | # When using the git backend branches and tags are translated into salt | ||
352 | # environments. | ||
353 | # Note: file:// repos will be treated as a remote, so refs you want used must | ||
354 | # exist in that repo as *local* refs. | ||
355 | # | ||
356 | # The gitfs_root option gives the ability to serve files from a subdirectory | ||
357 | # within the repository. The path is defined relative to the root of the | ||
358 | # repository and defaults to the repository root. | ||
359 | #gitfs_root: somefolder/otherfolder | ||
360 | |||
361 | |||
362 | ##### Pillar settings ##### | ||
363 | ########################################## | ||
364 | # Salt Pillars allow for the building of global data that can be made selectively | ||
365 | # available to different minions based on minion grain filtering. The Salt | ||
366 | # Pillar is laid out in the same fashion as the file server, with environments, | ||
367 | # a top file and sls files. However, pillar data does not need to be in the | ||
368 | # highstate format, and is generally just key/value pairs. | ||
369 | |||
370 | #pillar_roots: | ||
371 | # base: | ||
372 | # - /srv/pillar | ||
373 | |||
374 | #ext_pillar: | ||
375 | # - hiera: /etc/hiera.yaml | ||
376 | # - cmd_yaml: cat /etc/salt/yaml | ||
377 | |||
378 | # The pillar_opts option adds the master configuration file data to a dict in | ||
379 | # the pillar called "master". This is used to set simple configurations in the | ||
380 | # master config file that can then be used on minions. | ||
381 | #pillar_opts: True | ||
382 | |||
383 | |||
384 | ##### Syndic settings ##### | ||
385 | ########################################## | ||
386 | # The Salt syndic is used to pass commands through a master from a higher | ||
387 | # master. Using the syndic is simple, if this is a master that will have | ||
388 | # syndic servers(s) below it set the "order_masters" setting to True, if this | ||
389 | # is a master that will be running a syndic daemon for passthrough the | ||
390 | # "syndic_master" setting needs to be set to the location of the master server | ||
391 | # to receive commands from. | ||
392 | |||
393 | # Set the order_masters setting to True if this master will command lower | ||
394 | # masters' syndic interfaces. | ||
395 | #order_masters: False | ||
396 | |||
397 | # If this master will be running a salt syndic daemon, syndic_master tells | ||
398 | # this master where to receive commands from. | ||
399 | #syndic_master: masterofmaster | ||
400 | |||
401 | # This is the 'ret_port' of the MasterOfMaster | ||
402 | #syndic_master_port: 4506 | ||
403 | |||
404 | # PID file of the syndic daemon | ||
405 | #syndic_pidfile: /var/run/salt-syndic.pid | ||
406 | |||
407 | # LOG file of the syndic daemon | ||
408 | #syndic_log_file: syndic.log | ||
409 | |||
410 | ##### Peer Publish settings ##### | ||
411 | ########################################## | ||
412 | # Salt minions can send commands to other minions, but only if the minion is | ||
413 | # allowed to. By default "Peer Publication" is disabled, and when enabled it | ||
414 | # is enabled for specific minions and specific commands. This allows secure | ||
415 | # compartmentalization of commands based on individual minions. | ||
416 | |||
417 | # The configuration uses regular expressions to match minions and then a list | ||
418 | # of regular expressions to match functions. The following will allow the | ||
419 | # minion authenticated as foo.example.com to execute functions from the test | ||
420 | # and pkg modules. | ||
421 | # | ||
422 | #peer: | ||
423 | # foo.example.com: | ||
424 | # - test.* | ||
425 | # - pkg.* | ||
426 | # | ||
427 | # This will allow all minions to execute all commands: | ||
428 | # | ||
429 | #peer: | ||
430 | # .*: | ||
431 | # - .* | ||
432 | # | ||
433 | # This is not recommended, since it would allow anyone who gets root on any | ||
434 | # single minion to instantly have root on all of the minions! | ||
435 | |||
436 | # Minions can also be allowed to execute runners from the salt master. | ||
437 | # Since executing a runner from the minion could be considered a security risk, | ||
438 | # it needs to be enabled. This setting functions just like the peer setting | ||
439 | # except that it opens up runners instead of module functions. | ||
440 | # | ||
441 | # All peer runner support is turned off by default and must be enabled before | ||
442 | # using. This will enable all peer runners for all minions: | ||
443 | # | ||
444 | #peer_run: | ||
445 | # .*: | ||
446 | # - .* | ||
447 | # | ||
448 | # To enable just the manage.up runner for the minion foo.example.com: | ||
449 | # | ||
450 | #peer_run: | ||
451 | # foo.example.com: | ||
452 | # - manage.up | ||
453 | |||
454 | |||
455 | ##### Logging settings ##### | ||
456 | ########################################## | ||
457 | # The location of the master log file | ||
458 | # The master log can be sent to a regular file, local path name, or network | ||
459 | # location. Remote logging works best when configured to use rsyslogd(8) (e.g.: | ||
460 | # ``file:///dev/log``), with rsyslogd(8) configured for network logging. The URI | ||
461 | # format is: <file|udp|tcp>://<host|socketpath>:<port-if-required>/<log-facility> | ||
462 | #log_file: /var/log/salt/master | ||
463 | #log_file: file:///dev/log | ||
464 | #log_file: udp://loghost:10514 | ||
465 | |||
466 | #log_file: /var/log/salt/master | ||
467 | #key_logfile: /var/log/salt/key | ||
468 | |||
469 | # The level of messages to send to the console. | ||
470 | # One of 'garbage', 'trace', 'debug', info', 'warning', 'error', 'critical'. | ||
471 | #log_level: warning | ||
472 | |||
473 | # The level of messages to send to the log file. | ||
474 | # One of 'garbage', 'trace', 'debug', info', 'warning', 'error', 'critical'. | ||
475 | #log_level_logfile: warning | ||
476 | |||
477 | # The date and time format used in log messages. Allowed date/time formating | ||
478 | # can be seen here: http://docs.python.org/library/time.html#time.strftime | ||
479 | #log_datefmt: '%H:%M:%S' | ||
480 | #log_datefmt_logfile: '%Y-%m-%d %H:%M:%S' | ||
481 | |||
482 | # The format of the console logging messages. Allowed formatting options can | ||
483 | # be seen here: http://docs.python.org/library/logging.html#logrecord-attributes | ||
484 | #log_fmt_console: '[%(levelname)-8s] %(message)s' | ||
485 | #log_fmt_logfile: '%(asctime)s,%(msecs)03.0f [%(name)-17s][%(levelname)-8s] %(message)s' | ||
486 | |||
487 | # This can be used to control logging levels more specificically. This | ||
488 | # example sets the main salt library at the 'warning' level, but sets | ||
489 | # 'salt.modules' to log at the 'debug' level: | ||
490 | # log_granular_levels: | ||
491 | # 'salt': 'warning', | ||
492 | # 'salt.modules': 'debug' | ||
493 | # | ||
494 | #log_granular_levels: {} | ||
495 | |||
496 | |||
497 | ##### Node Groups ##### | ||
498 | ########################################## | ||
499 | # Node groups allow for logical groupings of minion nodes. | ||
500 | # A group consists of a group name and a compound target. | ||
501 | # | ||
502 | #nodegroups: | ||
503 | # group1: 'L@foo.domain.com,bar.domain.com,baz.domain.com and bl*.domain.com' | ||
504 | # group2: 'G@os:Debian and foo.domain.com' | ||
505 | |||
506 | |||
507 | ##### Range Cluster settings ##### | ||
508 | ########################################## | ||
509 | # The range server (and optional port) that serves your cluster information | ||
510 | # https://github.com/grierj/range/wiki/Introduction-to-Range-with-YAML-files | ||
511 | # | ||
512 | #range_server: range:80 | ||
513 | |||
514 | |||
515 | ##### Windows Software Repo settings ##### | ||
516 | ############################################## | ||
517 | # Location of the repo on the master | ||
518 | #win_repo: '/srv/salt/win/repo' | ||
519 | |||
520 | # Location of the master's repo cache file | ||
521 | #win_repo_mastercachefile: '/srv/salt/win/repo/winrepo.p' | ||
522 | |||
523 | # List of git repositories to include with the local repo | ||
524 | #win_gitrepos: | ||
525 | # - 'https://github.com/saltstack/salt-winrepo.git' | ||