Snippets are bad for many reasons and good for few, so can we narrow this down to just the problems that need to be solved and design something around that?
My understanding is: you'd like a way to point MAAS's HTTP proxy at an upstream proxy, but with a list of exceptions, addresses that should be fetched directly by MAAS's proxy.
That should be fairly easy to accomplish, and configurable via MAAS, but it also introduces the idea of MAAS as a general purpose front-end to SQUID, and I don't think that's a road we want to travel.
We could solve this discreetly by adding "include /var/lib/maas/maas-proxy.conf.d/*.conf" to the end of the template we use to generate the proxy configuration. I haven't tried it but, supposing it works, would that be acceptable?
Snippets are bad for many reasons and good for few, so can we narrow this down to just the problems that need to be solved and design something around that?
My understanding is: you'd like a way to point MAAS's HTTP proxy at an upstream proxy, but with a list of exceptions, addresses that should be fetched directly by MAAS's proxy.
That should be fairly easy to accomplish, and configurable via MAAS, but it also introduces the idea of MAAS as a general purpose front-end to SQUID, and I don't think that's a road we want to travel.
We could solve this discreetly by adding "include /var/lib/ maas/maas- proxy.conf. d/*.conf" to the end of the template we use to generate the proxy configuration. I haven't tried it but, supposing it works, would that be acceptable?