While I agree that adding support for --timeout would be useful, IMO, we should also ensure that the caller (i.e. Puppet manifests) waits for the openstackclient process to end, rather than just spawning a new processes.
It would also be nice if we could enforce such call timeout at the Puppet level, as we see not all things we call support timeout on their own. E.g. similar to subprocess.call() in Python - https://docs.python.org/3.4/library/subprocess.html#subprocess.call
While I agree that adding support for --timeout would be useful, IMO, we should also ensure that the caller (i.e. Puppet manifests) waits for the openstackclient process to end, rather than just spawning a new processes.
It would also be nice if we could enforce such call timeout at the Puppet level, as we see not all things we call support timeout on their own. E.g. similar to subprocess.call() in Python - https:/ /docs.python. org/3.4/ library/ subprocess. html#subprocess .call