Thanks for the explanation Ryan! I feel that there must be a better way, such as the apt proxy working with non-standard apt sources without issues. But wanting to disable any existing apt proxy in a charm does make sense.
What if debian-installer were changed to always use /etc/apt/apt.conf.d/10proxy? Although there would still be no guarantee if that file doesn't exist that there is no proxy configured some other way, and the same charm might conceivably run on some other service provider's cloud instance with a proxy set in some other way. Changing this task to debian-installer for consideration nevertheless. But we should have a separate upstream MAAS bug to add a configurable proxy. You mentioned existing bugs, but I can't find one. Do you have a bug number, or shall we create a separate bug if not? ** Package changed: maas (Ubuntu) => debian-installer (Ubuntu) ** Summary changed: - HTTP proxy config being created in /etc/apt/apt.conf on nodes + d-i should use apt.conf.d instead of adding proxy to apt.conf directly -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1060900 Title: d-i should use apt.conf.d instead of adding proxy to apt.conf directly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1060900/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
