cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Doc: playbook keywords are reserved names too (#69585)

Browse source
This commit is contained in:
Pilou 2020-05-28 15:32:28 +00:00 committed by GitHub
parent 187de7a8aa
commit 59f2174c8b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/docsite/rst/user_guide/playbooks_variables.rst
View file

@ -18,7 +18,7 @@ Once you understand the concepts and examples on this page, read about :ref:`Ans
Creating valid variable names
=============================
Not all strings are valid Ansible variable names. A variable name must start with a letter, and can only include letters, numbers, and underscores. `Python keywords`_ are not valid variable names.
Not all strings are valid Ansible variable names. A variable name must start with a letter, and can only include letters, numbers, and underscores. `Python keywords`_ and :ref:`playbook keywords<playbook_keywords>` are not valid variable names.
.. table::
:class: documentation-table
@ -28,6 +28,8 @@ Not all strings are valid Ansible variable names. A variable name must start wit
====================== ====================================================================
``foo`` ``*foo``, `Python keywords`_ such as ``async`` and ``lambda``
``foo_env`` :ref:`playbook keywords<playbook_keywords>` such as ``environment``
``foo_port`` ``foo-port``, ``foo port``, ``foo.port``
``foo5`` ``5foo``, ``12``