We are not interested in entertaining this feature because it takes playbooks into what I'd consider a sketchy programming territory.
For instance, Perl allowed $$x to mean "the value of the variable with the name of the value of x". This is a slippery slope we wish to avoid. Can we step back and try to understand what the use case of the IT solution you are trying to model is? Then another solution may jump out. On Fri, Jun 20, 2014 at 6:34 AM, <[email protected]> wrote: > Hi, > > See https://github.com/ansible/ansible/pull/7838 for a description of the > problem. > Unfortunately the solution proposed in the pull request was rejected. > Does anyone know a way to get this to work? > > Thanks. > > - Remco > > -- > 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/b4c4d0d3-5f7c-4b5e-8034-5a8f1572736f%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/b4c4d0d3-5f7c-4b5e-8034-5a8f1572736f%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/CA%2BnsWgzOrDouAs3N3o1pE2%3D05fjgBBudONPx%2B%3Dd2U4HquVxVkw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
