juju run doesn't have an option to trigger debug-hooks

[Michael Nelson]

juju run provides a great way to do not just small one-off commands, but also enables doing more complicated things - for example, applying an ansible playbook to do a rolling upgrade (ie. just upgrade the application service on one unit).

With that in mind, it'd be very helpful to be able to do:

juju run --unit elasticsearch/0 hooks/my-custom-hook --debug-hooks

I realise it's not really a hook, but given that it runs in a hook context, I can only test/debug it by triggering some other hook (config-changed).

[Andrew Wilkins (axwalk)]

Can you please expand on the use case a bit? You can run hooks from juju run --unit. What do you want with debug-hooks?

[Michael Nelson (michael.nelson)]

On Fri, Feb 14, 2014 at 5:05 AM, Andrew Wilkins
<email address hidden> wrote:
> Can you please expand on the use case a bit? You can run hooks from juju
> run --unit. What do you want with debug-hooks?

I want to debug a custom command that i run via juju run. ie. I want
to be able to do:

In terminal 1:
juju debug-hooks elasticsearch/0

In terminal 2:
juju run --unit elasticsearch/0 scripts/my-custom-command --debug-hooks

and have terminal 1 pick up the trigger and drop me into a screen for
scripts/my-custom-command so I can run it by hand and test the
environment. It's not a priority at all for me - I can always trigger
a hook context for debug-hooks via `juju set` and run my custom
command from there to debug, it was just a small thought of an
improvement.

[Stuart Bishop (stub)]

Has this been solved with actions? Or has the scope of this bug changed?

[Anastasia (anastasia-macmood)]

It looks like it may have been solved with actions. Marking as Incomplete until we get contrary feedback.

[Launchpad Janitor (janitor)]

[Expired for juju-core because there has been no activity for 60 days.]