Proposed API Change - Get default repo/namespace from environment variable.
Gustavo Niemeyer
gustavo.niemeyer at canonical.com
Tue Feb 28 22:31:05 UTC 2012
Hey Clint,
> 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
That sounds reasonable.
> export JUJU_CHARM_NAMESPACE=local
Sounds reasonable too, but I suggest that we call it JUJU_DEFAULT_NS,
and allow it to take one of the following forms:
1) scheme: (not "scheme" without colon.. that's potentially ambiguous
with series)
2) scheme:series or scheme:series/ (e.g. local:oneiric, or cs:oneiric/)
3) scheme:~user/series, or scheme:~user/series/ (e.g. cs:~spamaps/oneiric/)
If the variable is set, it will alter the way that charm names are
resolved when information is missing (no scheme, or no series). The
resolution algorithm should use the provided values and follow up from
there as it would for the values still missing.
How does that sound to everybody?
> 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.
I suggest putting that documentation in the command help (e.g. juju
deploy --help should show it), in addition to the online docs.
--
Gustavo Niemeyer
http://niemeyer.net
http://niemeyer.net/plus
http://niemeyer.net/twitter
http://niemeyer.net/blog
-- I'm not absolutely sure of anything.
More information about the Juju
mailing list