Merge pull request #3723 from archtaku/docs

Add notes on requisite matching

doc/ref/states/ordering.rst

@@ -49,6 +49,14 @@ The requisite system works by finding the states that are required and
 executing them before the state that requires them. Then the required states
 can be evaluated to see if they have executed correctly.
 
+.. note:: Requisite matching
+
+    Requisites match on both the ID Declaration and the ``name`` parameter.
+    Therefore, if you are using the ``pkgs`` or ``sources`` argument to install
+    a list of packages in a pkg state, it's important to note that you cannot
+    have a requisite that matches on an individual package in the list.
+
+
 Multiple Requisites
 -------------------
 

doc/ref/states/requisites.rst

@@ -43,6 +43,20 @@ the other way around. The vim package is saying "/etc/vimrc depends on me".
 In the end a single dependency map is created and everything is executed in a
 finite and predictable order.
 
+.. note:: Requisite matching
+
+    Requisites match on both the ID Declaration and the ``name`` parameter.
+    This means that in the example above, the ``require_in`` requisite would
+    also have been matched if the ``/etc/vimrc`` state was written as follows:
+
+    .. code-block:: yaml
+
+        vimrc:
+          file.managed:
+            - name: /etc/vimrc
+            - source: salt://edit/vimrc
+
+
 Requisite and Requisite in types
 ================================