Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Extends 'which notation should I use' section in FAQ #43729

Merged
merged 2 commits into from
Aug 30, 2018
Merged

Extends 'which notation should I use' section in FAQ #43729

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
81e6bc8
Extends 'which notation should I use' section in FAQ
ctorgalson Aug 6, 2018
b260225
Corrects rst link
ctorgalson Aug 30, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/docsite/rst/reference_appendices/faq.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -452,8 +452,10 @@ Ansible supports dot notation and array notation for variables. Which notation s
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The dot notation comes from Jinja and works fine for variables without special
characters. If your variable contains dots (.), colons (:), or dashes (-) it is
safer to use the array notation for variables.
characters. If your variable contains dots (.), colons (:), or dashes (-), if
a key begins and ends with two underscores, or if a key uses any of the known
public attributes, it is safer to use the array notation. See :ref:`playbooks_variables`
for a list of the known public attributes.

.. code-block:: jinja

Expand Down