cmd: add jujut (juju testing)

cmd: add jujut (juju testing)

jujut is a small tool I wrote to push values into the state
to test the provisioning agent. It doesn't replace unit tests
and is not intended to be shipped to customers. 

It has value for me, and if accepted, I expect to be replaced at 
some point when we have jujuc working.

https://code.launchpad.net/~dave-cheney/juju/go-command-jujut/+merge/107902

(do not edit description out of merge proposal)

[dave_cheney.net, 2012-05-30 01:44:49]

Please take a look.

[fwereade, 2012-05-30 07:04:29]

I'm -1 on this at the moment... it seems to have a fair amount of code
duplicated from elsewhere, and I really don't see what it gives us (that
couldn't/shouldn't be exercised by actual unit tests). A bit more context might
help me see the point...

[dave_cheney.net, 2012-05-30 07:12:17]

I used these commands while testing the PA, I thought they might be
useful for others.

If there no general need then i'll keep them in leave them in my
working directory.

On Wed, May 30, 2012 at 5:04 PM,  <fwereade@gmail.com> wrote:
> I'm -1 on this at the moment... it seems to have a fair amount of code
> duplicated from elsewhere, and I really don't see what it gives us (that
> couldn't/shouldn't be exercised by actual unit tests). A bit more
> context might help me see the point...
>
> http://codereview.appspot.com/6243070/

[dave_cheney.net, 2012-06-01 06:43:11]

Please take a look.

[niemeyer, 2012-06-06 12:22:46]

I agree with William. Even without seeing his comments, we had already debated
about the low level of automated testing in the provisioning agent. The use of
this tool is a side effect of doing one-off tests manually rather than
introducing proper logic onto the tests that continue to be run after it is
integrated.

From another perspective, some of these commands should be actual commands of
juju. add-machine and remove-machine are two great candidates for living on the
real command line suite.

[dave_cheney.net, 2012-06-06 12:31:42]

Sounds fair, i'll put this code on ice until we need them for juju cli.

On Wed, Jun 6, 2012 at 10:22 PM,  <n13m3y3r@gmail.com> wrote:
> I agree with William. Even without seeing his comments, we had already
> debated about the low level of automated testing in the provisioning
> agent. The use of this tool is a side effect of doing one-off tests
> manually rather than introducing proper logic onto the tests that
> continue to be run after it is integrated.
>
> From another perspective, some of these commands should be actual
> commands of juju. add-machine and remove-machine are two great
> candidates for living on the real command line suite.
>
> https://codereview.appspot.com/6243070/