setting up system proxy via cloud-config might be nice

This bug was originally filed in Launchpad as [LP: #1089405](https://bugs.launchpad.net/cloud-init/+bug/1089405)

Launchpad details

affected_projects = []

assignee = None

assignee_name = None

date_closed = 2022-07-05T12:02:25.619593+00:00

date_created = 2012-12-12T14:27:58.888667+00:00

date_fix_committed = None

date_fix_released = None

id = 1089405

importance = wishlist

is_complete = True

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1089405

milestone = None

owner = smoser

owner_name = Scott Moser

private = False

status = opinion

submitter = smoser

submitter_name = Scott Moser

tags = ['sts']

duplicates = []

_Launchpad user **Scott Moser(smoser)** wrote on 2012-12-12T14:27:58.888667+00:00_

as seen in bug 1089389 it might be nice to set system wide proxy information. There seems to be reasonable explanation of how you'd do that at [1].
Config could look like:

system_proxy:
 http_proxy: http://foo.bar:3128
 https_proxy: https://foo.host:3128
 ftp_proxy: ...
 no_proxy: ...

cloud-init would/should take just the lower case and write /etc/environment correctly.

Some tricky things here:
 a.) cloud-init should then adjust its own environment to use these settings (and subprocesses)
 b.) what about the datasource? ie, should / would access to http://169.254.169.254 be proxied?

[1] http://askubuntu.com/questions/150210/how-do-i-set-systemwide-proxy-servers-in-xubuntu-lubuntu-or-ubuntu-studio