Comment 4 for bug 1460151

I just verified - I deployed maas 1.7.5+bzr3369-0ubuntu1~trusty1 from maas stable ppa. It installed maas-proxy.
I haven't configured http proxy in maas.

When I deploy new nodes I get maas-proxy IP address in /etc/apt/apt.conf.d/90curtin-aptproxy.
If I then configure http proxy in MAAS (under "Network Configuration" -> "Proxy for HTTP and HTTPS traffic"), and deploy another node, that deployed node has http proxy I just configured in 90curtin-aptproxy.

So, in that manner I can control what to put as Apt::Http::Proxy in apt configuration, via MAAS. However, I can not 'disable' it (and let juju, for instance, take care of it).

Also, as I'm running apt-cacher-ng as an apt proxy (which for me behaves way better than squid), MAAS won't be able to download new boot images, as those don't reside in apt-cacher-ng.

There should definitely be an option push separate Apt::Http::Proxy configuration to the deployed nodes. That way user can choose not to let MAAS push that info altogether.