replied to the ticket, thanks
On Tue, Jul 29, 2014 at 1:42 PM, Garrett Plasky
wrote:
> Seems I crossed streams a bit with Serge's patch, apologies.
>
> I've re-submitted my testing which reproduces the problem as a new issue:
>
> https://github.com/ansible/ansible/issues/8340
>
>
> On Saturday,
Seems I crossed streams a bit with Serge's patch, apologies.
I've re-submitted my testing which reproduces the problem as a new issue:
https://github.com/ansible/ansible/issues/8340
On Saturday, July 26, 2014 4:08:43 PM UTC-7, michael wrote:
>
> vars_files paths that depend on a *inventory* scop
vars_files paths that depend on a *inventory* scoped variable name are
loaded differently than those that do not, though most are loaded at global
scope and that would happen only once. The inventory ones would happen
once per host and that could be a lot of math for large host counts, but
even so
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 Ginderacht
On Saturday, July 26, 2014 3:08:17 AM UTC-7, Serge van Ginderachter wrote:
>
>
> On 26 July 2014 00:57, Garrett Plasky >
> 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 w
On 26 July 2014 00:57, Garrett Plasky 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
+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 i
I'm open to the idea of parse_yaml_from_file caching small files in memory
if vault decoded.
On Thu, Jun 5, 2014 at 2:33 PM, Serge van Ginderachter <
se...@vanginderachter.be> wrote:
> I have a couple of patches in queue that might help on this (though not
> the core issue if the extra time i
