As we discussed, this should be a first class option, for a few reasons:
1) It's simpler. The interface for proxy selection should be:
juju bootstrap --http-proxy=$URL
2) We want control over that URL.
Even though we'll be using cloud-init for the moment, we'll also want to enable the user
to *change* that URL with a command like "juju set-env http-proxy=$URL", and that should
affect both the future machines, and the *current* machines, which cloud-init does not
do.
With those said, at some point we may want to enable a generic mechanism for preparing
machines, but this bug isn't justification for it.
As we discussed, this should be a first class option, for a few reasons:
1) It's simpler. The interface for proxy selection should be:
juju bootstrap --http-proxy=$URL
2) We want control over that URL.
Even though we'll be using cloud-init for the moment, we'll also want to enable the user
to *change* that URL with a command like "juju set-env http-proxy=$URL", and that should
affect both the future machines, and the *current* machines, which cloud-init does not
do.
With those said, at some point we may want to enable a generic mechanism for preparing
machines, but this bug isn't justification for it.