Proposed API Change - Get default repo/namespace from environment variable.

Clint Byrum clint at
Tue Feb 28 08:42:29 UTC 2012

Hi everybody,

While working on automating tests with juju, its become clear that some of
the stuff suggested in the test runner part of the spec an be very easily
done in Juju core with a small enhancement to the command line tools.

Basically, I'd like deploy and upgrade-charm to take a default repository
and charm namespace from an environment variable.

This allows us to not have to wrap juju in so intrusive a way. We can
just run the test script with special environment variables. So:

export JUJU_REPOSITORY=/path/to/testing/repo
juju deploy mysql

Will deploy from the local repo, whereas running the same test without
the special env will install from the charm store.

I've proposed two merges to accomplish this:

One side note, I didn't find a good place to document these environment
variables.  Perhaps we can resurrect the man page, or find a place in
docs/source for it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: review-diff.txt
Type: application/octet-stream
Size: 2899 bytes
Desc: not available
URL: <>

More information about the Juju mailing list