Makes sense. If it weren't for backwards compatibility I would definitely vote duration is machine readable, but maybe that's an issue with str(timedelta). Guess I'll just use regex 🤷
On Tue, Aug 3, 2021 at 1:31 PM Brian Coca <bc...@redhat.com> wrote: > Understood, we were not aware of the python bug when closing the > ticket, but a custom filter should work as well. > > One of the performance bottlenecks we find is in module return data > serialization/unserialization and memory ballooning (since registered > vars are kept through the life of the run), so we are now very > conservative on adding more fields to module returns if they can be > calculated with existing information on the controller side. > > Since now we have datetime filters, we would not add the current > 'delta' field to command anymore since start/end information is > already there. > > -- > ---------- > Brian Coca > > -- 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, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CADKG7DB2Jvk3x41Kw4DxWt-VFQhJ1FZiE_N8H7%2B_kJ%2Bd6Uz%3D7g%40mail.gmail.com.
