Discussed with: ad@

Shell access is sufficient, I see absolutely no value in this.

(configd) flush script output to tempfile to avoid the use of subprocess.check_output which can be slow on some platforms.

refuses to take /usr/local/bin into account, which kind of defeats
the purpose of using the portable "env" command...

when using the shell, it's now possible to trigger configd actions in a more natrual way, for example:

configdctl configd actions

(to list all registered actions)