a-c-m
/
community.general
mirror of https://github.com/ansible-collections/community.general.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Improve YAMLSyntax/Gotchas (#21575) 

* Improve YAMLSyntax/Gotchas

Colons don't need to be quoted unless when followed by a space or the end of the line

* Update YAMLSyntax.rst

Minor edit.
pull/4420/head
Marko Stanković 2017-03-03 21:49:03 +01:00 committed by scottb
parent 7018aa3316
commit 10125d520d
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/docsite/rst/YAMLSyntax.rst
View File

@ -123,11 +123,19 @@ While YAML is generally friendly, the following is going to result in a YAML syn
foo: somebody said I should put a colon here: so I did foo: somebody said I should put a colon here: so I did
You will want to quote any hash values using colons, like so:: windows_drive: c:
...but this will work::
windows_path: c:\windows
You will want to quote hash values using colons followed by a space or the end of the line::
foo: "somebody said I should put a colon here: so I did" foo: "somebody said I should put a colon here: so I did"
windows_drive: "c:"
And then the colon will be preserved. ...and then the colon will be preserved.
Further, Ansible uses "{{ var }}" for variables. If a value after a colon starts Further, Ansible uses "{{ var }}" for variables. If a value after a colon starts
with a "{", YAML will think it is a dictionary, so you must quote it, like so:: with a "{", YAML will think it is a dictionary, so you must quote it, like so::