juju-log vs. command line length limits

[Stuart Bishop]

juju-log currently requires the log message to be passed on the command line. This means that hooks can unexpectedly fail if they manage to exceed the maximum command line length.

This problem could be worked around if juju-log was able to read in the log message from stdin. This would also be useful in other situations too:

./long-running-task 2> >(juju-log -l ERROR --pipe 1>&2) > >(juju-log -l DEBUG --pipe)

[Andreas Hasenack (ahasenack)]

Not only that, if you have something like this:
"""
output=$(some command)
# output has "-e: option unknown"
juju-log "$output"
"""

juju-log won't log the output, but an error of its own (since it doesn't know the -e option).

[Eric Snow (ericsnowcurrently)]

For a similar issue with relation-set (and a possible solution), see lp:1437366.

[Gui Bot (rick-harding+guibot)]

Also true per email thread to the Juju list on action-set. I'd like to suggest we make this a generic bug for this whole pattern and identify all paths this can occur in and copy the file based approach used in the bug Eric links above in comment #2.

[John A Meinel (jameinel)]

Hi Gui-bot :)

Does juju-log support "--" so you can do:

juju-log -- "$output"
?

It would make pretty good sense to have juju log be able to read from stdin (output | juju-log -) or something similar.

[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.