This generally isn't something we'd force a dot release for, unless we otherwise thought we needed to cut a dot release.
If we did, we'd likely wait longer as well. On Sat, Nov 30, 2013 at 8:19 AM, Anand Buddhdev <[email protected]> wrote: > On Saturday, 30 November 2013 13:54:40 UTC+1, Michael DeHaan wrote: > > Hi Michael, > > Yep, I can replicate this. >> > > Oh, good :) > > >> include_vars is new for 1.4.X so we probably missed a possible use case >> that someone would want to try. >> >> Please file a github ticket. >> > > Filed as issue #5108 > > >> Meanwhile, you can work around this in a play like so: >> > > I don't need the work-around urgently, because we're using top-level > host_vars and group_vars. When you've fixed this bug, then I will rewrite > our playbooks and move those vars files directly into roles. Do you think > you will make a 1.4.2 release for this? In that case, I'm happy to just > wait a few days for it. > > Regards, > > Anand > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Michael DeHaan <[email protected]> CTO, AnsibleWorks, Inc. http://www.ansibleworks.com/ -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
