Skip to content

Commit

Permalink
Fix: build warnings (#689)
Browse files Browse the repository at this point in the history
Cleaned up some stray `make html` docs build warnings.

---------

Co-authored-by: Alex <aizquier@redhat.com>
  • Loading branch information
samccann and Alex-Izquierdo committed May 29, 2024
1 parent 2de0bae commit 857ce65
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 5 deletions.
10 changes: 6 additions & 4 deletions docs/conditions.rst
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ or other special characters:
action:
debug:
You can find more information about dot notation and bracket notation also in the Ansible playbook `manual <https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_variables.html#referencing-key-value-dictionary-variables>`_.
You can find more information about dot notation and bracket notation also in the Ansible playbook documentation for `Referencing key:value dictionary variables <https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_variables.html#referencing-key-value-dictionary-variables>`_.

You can access list in strutured event, fact, var data objects using bracket notation too.
The first item in a list is item 0, the second item is item 1.
Expand All @@ -96,7 +96,8 @@ For example:
action:
debug:
You can find more information the bracket notation for list also in the Ansible playbook `manual <https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_variables.html#referencing-list-variables>`_.
You can find more information the bracket notation for list also in the Ansible playbook
documentation for `Referencing list variables <https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_variables.html#referencing-list-variables>`_.

Supported Operators
*******************
Expand Down Expand Up @@ -863,7 +864,8 @@ Check if an item does not exist in a list based on a test
| The value is based on the operator used, if the operator is regex then the value is a pattern.
| If the operator is one of >,>=,<,<= then the value is either an integer or a float
You can find more information for the *select* condition also in the Ansible playbook `manual <https://docs.ansible.com/ansible/latest/playbook_guide/complex_data_manipulation.html#loops-and-list-comprehensions>`_.
You can find more information for the *select* condition also in the Ansible playbook
documentation for `Loops and list comprehensions <https://docs.ansible.com/ansible/latest/playbook_guide/complex_data_manipulation.html#loops-and-list-comprehensions>`_.

Checking if an object exists in a list based on a test
------------------------------------------------------
Expand Down Expand Up @@ -903,7 +905,7 @@ Checking if an object does not exist in a list based on a test
| If the operator is one of >, >=, <, <= then the value is either an integer or a float.
| If the operator is in or not in then the value is list of integer, float or string.
You can find more information for the *selectattr* condition also in the Ansible playbook `manual <https://docs.ansible.com/ansible/latest/playbook_guide/complex_data_manipulation.html#loops-and-list-comprehensions>`_.
You can find more information for the *selectattr* condition also in the Ansible playbook documentation for `Loops and list comprehensions <https://docs.ansible.com/ansible/latest/playbook_guide/complex_data_manipulation.html#loops-and-list-comprehensions>`_.


FAQ
Expand Down
2 changes: 1 addition & 1 deletion docs/filters.rst
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ Examples:
| The uuid stores the unique id for the event.
| The event payload would be modified to include the following data
.. code-block:: yaml
.. code-block:: python
event = { ..., 'meta': {'source': {'name': 'azure_service_bus',
'type': 'ansible.eda.azure_service_bus'},
Expand Down

0 comments on commit 857ce65

Please sign in to comment.