nestly say I was surprised too. I expected the opposite. These are
> questions that chew away at my days; Running endless performance profiling.
>
> On Mon, Mar 22, 2021 at 2:41 PM Alex Willmer wrote:
>
>> Huh, I would not have guessed that. Thanks, I'll try that nex
his discussion on the web visit
>> https://groups.google.com/d/msgid/ansible-devel/3a309938-189d-4b8b-b9c4-539afea81984n%40googlegroups.com
>> <https://groups.google.com/d/msgid/ansible-devel/3a309938-189d-4b8b-b9c4-539afea81984n%40googlegroups.com?utm_medium=email&utm_source=f
lo: 58:20:B1:0B:zz:zz
>
> PLAY RECAP ********
> ilo01 : ok=2changed=0unreachable=0failed=0
> ilo02 : ok=2changed=0unreachable=0failed=0
> ilo09 : ok=2
k additional
arguments.
Do you have a preference for json_query(..., mode=jq)?
Thanks, Alex
--
Alex Willmer
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, sen
On Thu, 31 Jan 2019 at 07:54, Georges Martin wrote:
> I would say yes. I already implemented such a filter around pyjq
>
Georges, can you release the code for your filter. I would save reinventing
the wheel.
With thanks, Alex
--
Alex Willmer
--
You received this message because y
*Abstract*
I would like to contribute a new jq() filter to Ansible, exposing the jq
expression language. This would complement the existing json_query()
filter, based on jmespath expressions. I wanted to see if such a filter
would be welcome, either as PR to Ansible itself, or a third party modu
