What are the (non-developers) use cases for --upload-tools
Gustavo Niemeyer
gustavo.niemeyer at canonical.com
Fri Mar 22 00:57:00 UTC 2013
Hi again Tim,
On Thu, Mar 21, 2013 at 6:23 PM, Tim Penhey <tim.penhey at canonical.com> wrote:
> In the first of my Friday morning emails, I'm trying to understand the
> use cases for --upload-tools.
>
> I've had it mentioned that --upload-tools is primarily used by
> developers, while developing.
>
> Are there use-cases for --upload-tools for non-developers? If so, what
> are they?
Right now there are none, because it indeed builds the tools, so you
need to have a developer environment at hand for it to work. The
original idea was to support sending the packaged binaries up as well,
so it can work anywhere that juju is found. This sounds like a nice
and easy property, given cases such as private cloud deployments.
> This leads me to another question:
> If --upload-tools is only for developers, should we remove the option
> from the packaged version? And if so, how?
I'd prefer a nice error message (as we have today?) than options
magically disappearing.
gustavo @ http://niemeyer.net
More information about the Juju-dev
mailing list