From 1199dff24638736a2401967eff9c37d5da07223b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yuma=20Inaura=20=28=E7=A8=B2=E6=B5=A6=E6=82=A0=E9=A6=AC=29?= Date: Thu, 26 Jul 2018 07:44:19 +0900 Subject: [PATCH] Update porting_guide_2.0.rst Fix indent +label: docsite_pr --- docs/docsite/rst/porting_guides/porting_guide_2.0.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/porting_guides/porting_guide_2.0.rst b/docs/docsite/rst/porting_guides/porting_guide_2.0.rst index 5761c559e1..9a84dd8ed9 100644 --- a/docs/docsite/rst/porting_guides/porting_guide_2.0.rst +++ b/docs/docsite/rst/porting_guides/porting_guide_2.0.rst @@ -107,7 +107,7 @@ Deprecated While all items listed here will show a deprecation warning message, they still work as they did in 1.9.x. Please note that they will be removed in 2.2 (Ansible always waits two major releases to remove a deprecated feature). -* Bare variables in ``with_`` loops should instead use the ``"{ {var }}"`` syntax, which helps eliminate ambiguity. +* Bare variables in ``with_`` loops should instead use the ``"{{ var }}"`` syntax, which helps eliminate ambiguity. * The ansible-galaxy text format requirements file. Users should use the YAML format for requirements instead. * Undefined variables within a ``with_`` loop's list currently do not interrupt the loop, but they do issue a warning; in the future, they will issue an error. * Using dictionary variables to set all task parameters is unsafe and will be removed in a future version. For example::