mirror of
https://github.com/valitydev/salt.git
synced 2024-11-08 09:23:56 +00:00
Merge pull request #16934 from basepi/prereqdocs16826
Fix pre-required vs pre-requiring mixups in prereq doc
This commit is contained in:
commit
a7815e2b35
@ -210,10 +210,10 @@ examples of "changes" dictionaries.)
|
||||
|
||||
If the "changes" key contains a populated dictionary, it means that the
|
||||
pre-required state expects changes to occur when the state is actually
|
||||
executed, as opposed to the test-run. The pre-required state will now
|
||||
actually run. If the pre-required state executes successfully, the
|
||||
pre-requiring state will then execute. If the pre-required state fails, the
|
||||
pre-requiring state will not execute.
|
||||
executed, as opposed to the test-run. The pre-requiring state will now
|
||||
actually run. If the pre-requiring state executes successfully, the
|
||||
pre-required state will then execute. If the pre-requiring state fails, the
|
||||
pre-required state will not execute.
|
||||
|
||||
If the "changes" key contains an empty dictionary, this means that changes are
|
||||
not expected by the pre-required state. Neither the pre-required state nor the
|
||||
|
Loading…
Reference in New Issue
Block a user