From 10125d520dfde00bafc10f123635de82158a1c5d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marko=20Stankovi=C4=87?= Date: Fri, 3 Mar 2017 21:49:03 +0100 Subject: [PATCH] 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. --- docs/docsite/rst/YAMLSyntax.rst | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/docs/docsite/rst/YAMLSyntax.rst b/docs/docsite/rst/YAMLSyntax.rst index 6aada5bb73b..894dd3838a4 100644 --- a/docs/docsite/rst/YAMLSyntax.rst +++ b/docs/docsite/rst/YAMLSyntax.rst @@ -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 -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" + + 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 with a "{", YAML will think it is a dictionary, so you must quote it, like so::