2016-02-03 19:13:15 +00:00
|
|
|
.. _blackout:
|
|
|
|
|
|
|
|
|
|
=============================
|
|
|
|
|
Minion Blackout Configuration
|
|
|
|
|
=============================
|
|
|
|
|
|
|
|
|
|
.. versionadded:: 2016.3.0
|
|
|
|
|
|
|
|
|
|
Salt supports minion blackouts. When a minion is in blackout mode, all remote
|
|
|
|
|
execution commands are disabled. This allows production minions to be put
|
|
|
|
|
"on hold", eliminating the risk of an untimely configuration change.
|
|
|
|
|
|
|
|
|
|
Minion blackouts are configured via a special pillar key, ``minion_blackout``.
|
|
|
|
|
If this key is set to ``True``, then the minion will reject all incoming
|
|
|
|
|
commands, except for ``saltutil.refresh_pillar``. (The exception is important,
|
|
|
|
|
so minions can be brought out of blackout mode)
|
2016-02-03 19:29:11 +00:00
|
|
|
|
|
|
|
|
Salt also supports an explicit whitelist of additional functions that will be
|
|
|
|
|
allowed during blackout. This is configured with the special pillar key
|
|
|
|
|
``minion_blackout_whitelist``, which is formed as a list:
|
|
|
|
|
|
2016-10-12 15:31:07 +00:00
|
|
|
.. code-block:: yaml
|
2016-02-03 19:29:11 +00:00
|
|
|
|
|
|
|
|
minion_blackout_whitelist:
|
|
|
|
|
- test.ping
|
|
|
|
|
- pillar.get
|
