plugins cannot error like juju commands

[Aaron Bentley]

When a juju command errors, it exits with a specific exit status. When a juju plugin errors, juju writes an additional message: "ERROR subprocess encountered error code $FOO". This means that plugins cannot behave quite like juju commands. It implies that something is wrong with the plugin, when in fact, nothing is wrong. It draws attention away from the actual error message.

For example, I've written a plugin "retry" that runs "juju resolved --retry":

# Actual command
$ juju resolved --retry apache2-reverseproxy
error: invalid unit name "apache2-reverseproxy"

# Plugin running the same command
$ juju retry apache2-reverseproxy
error: invalid unit name "apache2-reverseproxy"
ERROR subprocess encountered error code 2

# Plugin run without juju does not have the extra error message.
$ juju-retry apache2-reverseproxy
error: invalid unit name "apache2-reverseproxy"

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.