| /dports/sysutils/py-salt/salt-3004.1/tests/pytests/unit/state/ |
| H A D | test_multi_env_highstate.py | 38 def highstate( function
114 assert not highstate.avail._filled
115 assert highstate.avail._avail == {"base": None}
118 assert not highstate.avail._filled
143 assert not highstate.avail._filled
144 assert highstate.avail._avail == {"base": None}
147 assert highstate.avail._filled
172 assert not highstate.avail._filled
173 assert highstate.avail._avail == {"base": None}
176 assert not highstate.avail._filled
[all …]
|
| H A D | test_state_highstate.py | 62 def test_top_matches_with_list(highstate): argument
64 matches = highstate.top_matches(top)
68 def test_top_matches_with_string(highstate): argument
70 matches = highstate.top_matches(top)
74 def test_matches_whitelist(highstate): argument
76 matches = highstate.matches_whitelist(matches, ["state2"])
80 def test_matches_whitelist_with_string(highstate): argument
86 def test_compile_state_usage(highstate, state_tree_dir): argument
96 state_usage_dict = highstate.compile_state_usage()
172 matches = highstate.top_matches(top)
[all …]
|
| /dports/sysutils/py-salt/salt-3004.1/tests/pytests/unit/output/ |
| H A D | test_highstate.py | 2 import salt.output.highstate as highstate namespace
7 return {highstate: {"__opts__": {"strip_colors": True}}}
14 actual_output = highstate.output(data=data)
34 actual_output = highstate.output(data=data)
60 actual_output = highstate.output(data=data)
68 actual_output = highstate.output(data)
81 actual_output = highstate.output(data)
|
| /dports/sysutils/py-salt/salt-3004.1/salt/utils/ |
| H A D | state.py | 23 def search_onfail_requisites(sid, highstate): argument
32 for fstate, fchunks in highstate.items():
72 def check_onfail_requisites(state_id, state_result, running, highstate): argument
87 if state_id and state_result and highstate and isinstance(highstate, dict):
88 onfails = search_onfail_requisites(state_id, highstate)
115 def check_result(running, recurse=False, highstate=None): argument
140 ret = check_result(state_result, recurse=True, highstate=highstate)
145 check_onfail_requisites(state_id, state_result, running, highstate)
|
| H A D | pydsl.py | 153 highstate = self.included_highstate
167 HIGHSTATE.clean_duplicate_extends(highstate)
170 if state_id not in highstate:
173 for arg in highstate[state_id]["stateconf"]:
222 highstate = OrderedDict()
226 highstate["extend"] = extend = OrderedDict()
230 highstate[decl._id] = decl._repr()
235 highstate, self.included_highstate, errors
239 return highstate
241 def load_highstate(self, highstate):
[all …]
|
| /dports/sysutils/py-salt/salt-3004.1/tests/unit/output/ |
| H A D | test_highstate.py | 6 import salt.output.highstate as highstate
19 highstate: {
101 ret = highstate.output(self.data)
123 ret = highstate.output(self.data)
138 highstate: {
212 ret = highstate.output(self.data)
|
| /dports/sysutils/py-salt/salt-3004.1/doc/topics/tutorials/ |
| H A D | cron.rst | 6 The Salt Minion can initiate its own :ref:`highstate <running-highstate>` using
18 Use cron to initiate a highstate
28 The above cron entry will run a :ref:`highstate <running-highstate>` every day
|
| H A D | states_pt1.rst | 121 .. _running-highstate:
139 This action is referred to as a "highstate", and can be run using the
140 :py:func:`state.highstate <salt.modules.state.highstate>` function.
141 However, to make the usage easier to understand ("highstate" is not
144 when invoked without any SLS names will trigger a highstate.
145 :py:func:`state.highstate <salt.modules.state.highstate>` still exists and
151 SLS names will run :py:func:`state.highstate
152 <salt.modules.state.highstate>`
162 not be available in the top file until after the first :ref:`highstate
163 <running-highstate>`. To make custom grains available on a minion's first
[all …]
|
| /dports/sysutils/py-salt/salt-3004.1/doc/ref/states/ |
| H A D | startup.rst | 16 :ref:`highstate <running-highstate>`
30 :ref:`highstate <running-highstate>` when starting the minion:
34 startup_states: highstate
|
| H A D | top.rst | 191 files in the ``prod`` environment, run: ``salt '*' state.highstate
348 When a :ref:`highstate <running-highstate>` is executed and an environment is
350 passing the saltenv when executing the :ref:`highstate <running-highstate>`),
355 <running-highstate>` is executed without an environment specified.
381 when executing the highstate to avoid any complicated merging scenarios.
392 configuring a :ref:`highstate <running-highstate>`.
456 In this scenario, the :ref:`highstate <running-highstate>` was either invoked
459 environment will be part of the :ref:`highstate <running-highstate>`, and it
464 :ref:`highstate <running-highstate>`, and it would be applied to all minions.
466 If the ``qa`` environment were specified, the :ref:`highstate
[all …]
|
| H A D | layers.rst | 49 what the low state looks like for a :ref:`highstate <running-highstate>`, run:
106 .. _state-layers-highstate:
120 To execute the :ref:`highstate <running-highstate>` use :py:func:`state.apply
|
| /dports/sysutils/py-salt/salt-3004.1/doc/ref/file_server/ |
| H A D | environments.rst | 47 - :py:mod:`state.highstate <salt.modules.state.highstate>`
52 When the ``saltenv`` parameter is used to trigger a :ref:`highstate
53 <running-highstate>` using either :py:mod:`state.apply
54 <salt.modules.state.apply>` or :py:mod:`state.highstate
55 <salt.modules.state.highstate>`, only states from that environment will be
|
| /dports/sysutils/py-salt/salt-3004.1/tests/unit/returners/ |
| H A D | test_highstate_return.py | 13 import salt.returners.highstate_return as highstate namespace
34 highstate: {
115 highstate.returner(ret)
|
| /dports/sysutils/py-salt/salt-3004.1/doc/ref/output/all/ |
| H A D | salt.output.highstate.rst | 1 salt.output.highstate
4 .. automodule:: salt.output.highstate
|
| /dports/sysutils/py-salt/salt-3004.1/tests/unit/states/ |
| H A D | test_saltmod.py | 128 saltmod.state(name, tgt, highstate=True, concurrent="a"), ret
133 self.assertDictEqual(saltmod.state(name, tgt, highstate=True), test_ret)
166 self.assertDictEqual(saltmod.state(name, tgt, highstate=True), ret)
182 state_run = saltmod.state(name, tgt, highstate=True)
368 "state.sls", tgt="*", ssh=True, highstate=True, roster="my_roster"
|
| /dports/sysutils/py-salt/salt-3004.1/doc/topics/cloud/ |
| H A D | reactor.rst | 247 ``highstate``. This will tell the minion to immediately apply a :ref:`highstate
248 <running-highstate>`, as soon as it is able to do so.
259 :ref:`highstate <running-highstate>` would include configuration to block
262 and kicked off a :ref:`highstate <running-highstate>` run. Users have reported
277 And the following ``sls`` file will start a :ref:`highstate
278 <running-highstate>` run on the target minion:
288 itself, the :ref:`highstate <running-highstate>` run will not step on
|
| /dports/sysutils/py-salt/salt-3004.1/salt/renderers/ |
| H A D | pydsl.py | 377 highstate = dsl_sls.to_highstate(mod)
379 return highstate
|
| /dports/sysutils/py-salt/salt-3004.1/doc/topics/orchestrate/ |
| H A D | orchestrate_runner.rst | 7 Executing states or highstate on a minion is perfect when you want to ensure that
35 context. Whereas the ``state.sls``, ``state.highstate``, et al. functions are
44 The ``state.sls``, ``state.highstate``, et al. functions allow you to statefully
198 To run a highstate, set ``highstate: True`` in your state config:
206 - highstate: True
322 - highstate: True
482 "outputter": "highstate",
515 "out": "highstate"
549 "out": "highstate"
566 "out": "highstate"
[all …]
|
| /dports/sysutils/terraform/terraform-1.0.11/website/docs/language/resources/provisioners/ |
| H A D | salt-masterless.html.md | 55 tree](http://docs.saltstack.com/ref/states/highstate.html#the-salt-state-tree).
63 tree](http://docs.saltstack.com/ref/states/highstate.html#the-salt-state-tree).
66 - `custom_state` (string) - A state to be run instead of `state.highstate`.
67 Defaults to `state.highstate` if unspecified.
|
| /dports/sysutils/py-salt/salt-3004.1/doc/topics/targeting/ |
| H A D | pillar.rst | 16 :ref:`highstate <running-highstate>` run. Once Pillar data changes, you
|
| /dports/sysutils/py-salt/salt-3004.1/doc/topics/grains/ |
| H A D | index.rst | 140 will be distributed to the minions when :mod:`state.highstate
141 <salt.modules.state.highstate>` is run, or by executing the
193 :ref:`highstate <running-highstate>`. To make custom grains available on a
194 minion's first highstate, it is recommended to use :ref:`this example
297 :mod:`state.highstate <salt.modules.state.highstate>` is called, or (as noted
|
| /dports/net/freeradius3/freeradius-server-3.0.25/src/tests/salt-test-server/ |
| H A D | build.sh | 1 salt-ssh --config-dir=salt_config -l quiet "test-server" state.highstate
|
| /dports/sysutils/py-salt/salt-3004.1/doc/topics/development/modules/ |
| H A D | ssh_wrapper.rst | 32 and :py:func:`highstate <salt.modules.state.highstate>`. When executing ``salt-ssh minion state.hig…
|
| /dports/net-im/coccinella/Coccinella-0.96.20Src/jabber/ |
| H A D | Login.tcl | 849 upvar 0 $token highstate
851 set highstate(cmd) $cmd
852 set highstate(args) $args
853 set highstate(pending) 1
907 upvar 0 $token highstate
921 eval {SetStatus} $highstate(args)
938 unset highstate
|
| /dports/sysutils/py-salt/salt-3004.1/salt/client/ssh/wrapper/ |
| H A D | state.py | 82 def _set_retcode(ret, highstate=None): argument
93 if not salt.utils.state.check_result(ret, highstate=highstate):
505 return highstate(**kwargs)
647 def highstate(test=None, **kwargs): function
924 _set_retcode(ret, highstate=highstate)
|