Snap enterprise proxy support
Bug #1883830 reported by
Stéphane Graber
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
Just like MAAS supports configuring a traditional http proxy and supports changing package archive location for an internal mirror, it would be nice if I could give MAAS the URL and ID of my snap proxy and have it automatically configure the system it deploys to use it.
We're currently working around this by having every single CI script that uses MAAS then immediately configure the proxy too by pulling and running a shell script, but this doesn't cover any of the manually deployed systems which would also benefit from the proxy.
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Jerzy Husakowski (jhusakowski) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
The current way to do this with MAAS is to use cloud-init, and MAAS does not intend to alter the configuration of deployed systems in another way. The experience of configuring snapd to use on-prem store is about to change, so adding this to MAAS would not be a long-term improvement.