Pain Point: juju debug-hooks

[David Britton]

Hi All --

The landscape team has been testing and porting various charms to
juju-core, and one of the pain points has been the lack of juju
debug-hooks.  This has bitten us in many subtle ways:

 - You can't interactively debug quickly/easliy
 - You can't "try out" commands in a hook environment to introspect
relations, for example
 - Studying hook interaction between services (one of the hard parts of
juju) is difficult to understand without slowing things down with
debug-hooks.

The workaround at this point has been to modify scripts in place on the
deployed unit and then retry relations/installs to get it right.  As you
can imagine the lengthening of the debug cycle there is quite frustrating.
 Anyone in the community using juju-core is probably hitting the same
issues (just a guess).

Is there a way to implement something in this space?  Even if it's not as
nice and full featured as the pyjuju version, it would be quite welcome and
useful.

Thanks!

-- 
David Britton <david.britton at canonical.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130531/74c57c89/attachment.html>