Fix order of version_compare arguments in porting guide (#15809)

I struggled with this for quite a while trying to figure out the right quoting before I discovered that the arguments to `version_compare` were reversed.
pull/16806/head
Kevin Bullock 8 years ago committed by Brian Coca
parent 71c97685a1
commit 243af8f727

@ -26,7 +26,7 @@ To make an escaped string that will work on all versions you have two options::
uses key=value escaping which has not changed. The other option is to check for the ansible version::
"{{ (ansible_version|version_compare('ge', '2.0'))|ternary( 'test1_junk 1\\3' | regex_replace('(.*)_junk (.*)', '\\1 \\2') , 'test1_junk 1\\\\3' | regex_replace('(.*)_junk (.*)', '\\\\1 \\\\2') ) }}"
"{{ (ansible_version|version_compare('2.0', 'ge'))|ternary( 'test1_junk 1\\3' | regex_replace('(.*)_junk (.*)', '\\1 \\2') , 'test1_junk 1\\\\3' | regex_replace('(.*)_junk (.*)', '\\\\1 \\\\2') ) }}"
* trailing newline When a string with a trailing newline was specified in the
playbook via yaml dict format, the trailing newline was stripped. When

Loading…
Cancel
Save