no_echo prompt echoes value in error message

[luto]

- hosts: paternoster
  vars:
    parameters:
      - name: domain
        short: d
        type: paternoster.types.domain
        prompt: yes
        prompt_options:
          confirm: yes
          no_echo: yes

[root@centos-s-2vcpu-4gb-fra1-01 ~]# ./add-domain 
Domain: (enter "qwe")
Please confirm: (enter "qwe")
usage: add-domain [-h] [-d DOMAIN] [-v]
add-domain: error: argument -d/--domain: invalid domain value: 'qwe'

[brutus]

We are deep in Argparser territory here. The strings are printed by the exit
method form the ArgumentParser class. The logic that raises this is in the
internal _get_value methode:

def _get_value(self, action, arg_string):
    type_func = self._registry_get('type', action.type, action.type)
    if not _callable(type_func):
        msg = _('%r is not callable')
        raise ArgumentError(action, msg % type_func)

    # convert the value to the appropriate type
    try:
        result = type_func(arg_string)

    # ArgumentTypeErrors indicate errors
    except ArgumentTypeError:
        name = getattr(action.type, '__name__', repr(action.type))
        msg = str(_sys.exc_info()[1])
        raise ArgumentError(action, msg)

    # TypeErrors or ValueErrors also indicate errors
    except (TypeError, ValueError):
        name = getattr(action.type, '__name__', repr(action.type))
        msg = _('invalid %s value: %r')
        raise ArgumentError(action, msg % (name, arg_string))

[brutus]

One workaround could be to subclass the ArgumentParser class and override its error method, to raise errors as exception instead of printing and exiting, so that we could handle the output ourself and restrict it for no_echo options:

https://github.com/python/cpython/blob/a2665075cc2fb85129afdfd7a7f04dd70a38e582/Lib/argparse.py#L2364