Exactly, that's what I would probably do as well. Once you are within
a relation you want to wait for further actions, dump the
$JUJU_RELATION_ID into a file and wait until you want to wake it up
again. Hooks are guaranteed to be run in series, so you don't have to
worry about concurrency issues
The missing command here is relation-ids to list the relation ids of a
given relation name. JUJU_RELATION_ID gives the current relation be
executed for, to trigger/inspect state on other relations, the relation-ids
command can be used to find their id, which can be passed to
relation-get/set with
Hi Mike,
You cannot control the sequence in which the hooks are executed, but
you have full control of what you do when the hooks do execute. You
can choose to send nothing to the other side of the relation until its
time to report that a connection may now be established, and when you
do change
