[WIP] Start of flexible duration specification

[sivel]

SUMMARY

This PR aims to provide a more flexible duration spec for use in user input, instead of relying on the user providing an integer defining seconds, or in cases where a module accepts seconds and minutes as exclusive parameters.

Using this, a module could define:

from ansible.module_utils.parsing.duration import duration

module = AnsibleModule(
    argument_spec=dict(
        duration=dict(type=duration)
    )
)

The user would provide something like the following:

duration: 5m5s
duration: 1d
duration: 1m
duration: 60

The duration type function, returns a datetime.timedelta object, and if the module needs seconds it can rely on params['duration'].total_seconds()

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

lib/ansible/module_utils/parsing/duration.py

ANSIBLE VERSION

devel

ADDITIONAL INFORMATION

The human_time_delta and timedelta_to_dict functions probably don't belong in parsing, eventually they should move to text.format

[ansibot]

cc @AnderEnder @gregswift @jarv @jhoekx
click here for bot help

[ansibot]

The test ansible-test sanity --test pylint [explain] failed with 2 errors:

lib/ansible/module_utils/parsing/duration.py:9:0: anomalous-backslash-in-string Anomalous backslash in string: '\.'. String constant might be missing an r prefix.
lib/ansible/module_utils/parsing/duration.py:49:0: dangerous-default-value Dangerous default value [] as argument

click here for bot help

[rackergs]

looks legit to me but I'm pretty sure my +1 doesnt do anything in the system 😁

[sivel]

@rackergs thanks! and sorry for the ping. Meant to have the bot skip this for the time being.

[sivel]

bot_skip

[detobel36]

Any news about this ?

[webknjaz]

/azp run

[azure-pipelines]

Pull request contains merge conflicts.

[webknjaz]

/azp run

[azure-pipelines]

Pull request contains merge conflicts.