Is this specifically related to the args parameter? Or all variable content to tasks?
-tim On Jan 13, 2016 5:02 AM, "James Cammarata" <[email protected]> wrote: > The first message is for this: > > - some_module: > args: "{{some_var}}" > > This is, in our opinion, very unsafe - especially when that variable may > come from something like a fact. It has not been disabled, but will be > removed after 2 major versions. > > I was unaware of any feature where we silently converted Windows line > endings to POSIX-compliant versions, but you can open an issue in Github > for this. > > Finally, this may be an oversight, or a bug in which the deprecation > message for bare variables in loops is not being triggered correctly. This > is fairly minor, but we can look into that as well. > > James Cammarata > Director, Ansible Core Engineering > github: jimi-c > > On Tue, Jan 12, 2016 at 5:16 PM, Jacob Weber <[email protected]> wrote: > >> I'm trying my playbooks with Ansible 2.0, and ran into a few minor issues: >> >> - The Ansible upgrade guide says "Using variables for task parameters is >> unsafe and will be removed in a future version." What does this mean >> exactly? I use variables in task parameters all the time -- this seems >> fundamental to Ansible. Can you clarify this? Is it only when you define >> variables and use them in the same task, like in the example? >> >> - When my source and destination boxes are Linux, and I deployed a >> template with Windows line endings, they used to be converted to Unix line >> endings (in Ansible 1.9). Now the Windows line endings are preserved, but I >> didn't see this in the changelog. >> >> - The upgrade guide says I should receive a deprecation warning in this >> case: "Bare variables in with_ loops should instead use the “{{var}}” >> syntax, which helps eliminate ambiguity." But I'm not getting that warning >> for things like "with_items: some_variable". >> >> Thanks, >> >> Jacob >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ansible-project/d1961831-e6d5-4519-8fdf-4cf56240816c%40googlegroups.com >> <https://groups.google.com/d/msgid/ansible-project/d1961831-e6d5-4519-8fdf-4cf56240816c%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CAMFyvFiOVqia6MoSth1Kj4eWFo%3DepK7CW5R%2BVmj4qr2NLcficA%40mail.gmail.com > <https://groups.google.com/d/msgid/ansible-project/CAMFyvFiOVqia6MoSth1Kj4eWFo%3DepK7CW5R%2BVmj4qr2NLcficA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAB0Zv8jWQym1-Y%2BLpcppwnak0Ue4J2wQ-3bUNQC8KgLc0aASig%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
