If a hook tool is invoked as follows on a leader unit, application status gets updated in the Juju state but it does not get represented in the `juju status` output similar to unit status values:
juju run --unit apache-httpd/0 "status-set --application active 'httpd app is ready'"
juju status
Model Controller Cloud/Region Version SLA Timestamp
default localhost-localhost localhost/localhost 2.6.9 unsupported 11:39:07+03:00
App Version Status Scale Charm Store Rev OS Notes
apache-httpd active 1 apache-httpd local 2 ubuntu
dummy-vhost active 1 dummy-vhost local 4 ubuntu
Unit Workload Agent Machine Public address Ports Message
apache-httpd/0* active idle 0 10.190.92.84 httpd is ready
dummy-vhost/0* active idle 0 10.190.92.84 Dummy vhost is ready
Machine State DNS Inst id Series AZ Message
0 started 10.190.92.84 juju-382280-0 bionic Running
juju run --unit apache-httpd/0 'status-get --application --include-data'
application-status:
message: httpd app is ready
status: active
status-data: {}
units:
apache-httpd/0:
message: httpd is ready
status: active
status-data: {}
The application status message isn't very useful unless it can be seen by the end user.
Github PR: https:/