Further testing on the dev build reveals that the issue does not surface when using a vault-encrypted group_vars but still affects the usage of vars_files.
On Saturday, July 26, 2014 1:39:37 PM UTC-7, Garrett Plasky wrote: > > > > On Saturday, July 26, 2014 3:08:17 AM UTC-7, Serge van Ginderachter wrote: >> >> >> On 26 July 2014 00:57, Garrett Plasky <[email protected]> wrote: >> >>> +1 would love to see this patch get prioritized as this severely limits >>> the utility of vault files. As an example, a playbook running against one >>> group with ~500 hosts which in turn references a single vault-encrypted >>> file via vars_files, takes 6 1/2 minutes to run vs ~30 seconds when the >>> file is decrypted. >>> >> >> The patches I referred to earlier, have been merged in the mean time. Do >> you still see this behaviour using the latest devel branch? >> >> (This patch should make sure that encrypted file is only parsed once, >> where before it would get parsed again for every of those 500 hosts) >> >> >> >> Serge >> > > I can confirm the problem is still present in devel. I'll add details to > the open issue but I definitely don't see any improvement in my use case. > > $ ansible-playbook --version > ansible-playbook 1.7 (devel d51e10a3f4) last updated 2014/07/26 13:13:39 > (GMT -700) > -- 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/460c7c0f-e39a-4bba-a51a-91e5319ea192%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
