We can no longer decorate the output of varnishadm with our own. This is unavoidable as far as I know, with the limitations of Bash.
I even tried assigning STDOUT to FD3 and sending our decorations using >&3 echo invocations, but this causes all our decorations to either appear before all output emitted by varnishadm, or after, depending on the specific semantics used, but there is no way to interlace our output with that of varnishadm in the intuitive manner we expect (as previously).
Due to a bug in varnishadm, output cannot be suppressed when the commands are successful since any commands so sent via STDIN will always cause varnishadm to exit with 0 (success) status. See: varnishcache/varnish-cache/issues/4012.
This fixes #168, but comes with some trade-offs:
We can no longer decorate the output of
varnishadm
with our own. This is unavoidable as far as I know, with the limitations of Bash.I even tried assigning STDOUT to FD3 and sending our decorations using
>&3 echo
invocations, but this causes all our decorations to either appear before all output emitted byvarnishadm
, or after, depending on the specific semantics used, but there is no way to interlace our output with that ofvarnishadm
in the intuitive manner we expect (as previously).varnishadm
, output cannot be suppressed when the commands are successful since any commands so sent via STDIN will always causevarnishadm
to exit with 0 (success) status. See: varnishcache/varnish-cache/issues/4012.