From 2d63518753b92ec7a55a1fa492c35a8bd320b317 Mon Sep 17 00:00:00 2001 From: Michael Date: Tue, 30 May 2017 12:58:10 +0000 Subject: [PATCH] Fixed markdown in changelog.md (#22980) --- CHANGELOG.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 8ad0e3a0c68..9198a867648 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -48,12 +48,12 @@ Ansible Changes By Release hash mark was included as part of the string. Now it is treated as a trailing comment:: - # Before: - var1="string#comment" ===> var1: "\"string#comment\"" - var1="string" #comment ===> var1: "\"string\" #comment" - # After: - var1="string#comment" ===> var1: "string#comment" - var1="string" #comment ===> var1: "string" + # Before: + var1="string#comment" ===> var1: "\"string#comment\"" + var1="string" #comment ===> var1: "\"string\" #comment" + # After: + var1="string#comment" ===> var1: "string#comment" + var1="string" #comment ===> var1: "string" The new behaviour mirrors how the variables would appear if there was no hash mark in the string. @@ -1242,7 +1242,7 @@ Module fixes: * Backslashes used when specifying parameters in jinja2 expressions in YAML dicts sometimes needed to be escaped twice. This has been fixed so that escaping once works. Here's an example of how playbooks need to be modified: - ``` + ```yaml # Syntax in 1.9.x - debug: msg: "{{ 'test1_junk 1\\\\3' | regex_replace('(.*)_junk (.*)', '\\\\1 \\\\2') }}" @@ -1260,7 +1260,7 @@ format the trailing newlines were kept. In v2, both methods of specifying the string will keep the trailing newlines. If you relied on the trailing newline being stripped you can change your playbook like this: - ``` + ```yaml # Syntax in 1.9.2 vars: message: > @@ -1287,7 +1287,7 @@ variable syntax ('{{var_name}}') - bare variable names there are no longer accep In fact, even specifying args with variables has been deprecated, and will not be allowed in future versions: - ``` + ```yaml --- - hosts: localhost connection: local