Comment 1 for bug 1274584

It would be nice to improve the scope definition for this task. What's the goal?
To be clear, adding --upload-tools to quickstart is trivial. That said, IIUC this would represent a workaround for a MaaS limitation. Is this a structural limitation or a bug that will eventually be fixed? One of the quickstart goals is to only support stable versions of juju, in which usually --upload-tools is not required. This is good from the user experience perspective and also reduces code complexity. Moreover, while by now we are used to --upload-tools, from the quickstart users' point of view it doesn't seem easy to me to explain the underlying concept: it requires understanding of how juju-core works internally, and AFAICT it is supposed to be a development tool. I can agree on adding this kind of advanced flags, but I think the above must be considered before following that path. If we expect the MaaS issue not to be solved in the medium term, another option could be changing quickstart so that --upload-tools is automatically added to the bootstrap args if the provider type is maas: this is doable since quickstart already detected the env type when bootstrap is executed.