new_expire_time value is interpreted as integer

[peterdragun]

If I use default value for new_expire_time which is "+172800" this is interpreted as number 172800. Problem is that Tower expects either time to be added or timestamp in the future or exact time.
Reproducer:
using latest version of broker with not new_expire_time variable set in config or in config with +.
broker extend --all

[ogajduse]

If the new_expire_time is passed as a command-line argument, broker interprets it as string, which is correct.

[ogajduse]

This is a Dynaconf bug, but I would like to keep this one open until the Dynaconf issue is resolved.
dynaconf/dynaconf#585

[JacobCallahan]

the dynaconf issue has been resolved in the latest release

[ogajduse]

FYI, I just found out that the latest Dynaconf 3.1.7 does not include the fix yet.