Add proxy support for configuring ops man authentication

[wrast]

Newer versions of om allow setting http proxy, https proxy, and no proxy. These settings are missing from the current call to configure-authentication.

https://github.com/pivotal-cf/pcf-pipelines/blob/5f88a5e6786da30d3fc252626d30e4162379370a/tasks/config-opsman/task.sh#L10-L16

Proxy arguments allowed:

  --http-proxy-url              string  proxy for outbound HTTP network traffic
  --https-proxy-url             string  proxy for outbound HTTPS network traffic
  --no-proxy                    string  comma-separated list of hosts that do not go through the proxy

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

[abbyachau]

Hi @wrast thanks for raising this. Sorry about the delay in response. Did you run into this issue at a customer site? If so, could you please get in touch about the use case? Thanks.

[wrast]

Yes this was at a customer site. We worked around it ourselves by adding the 3 additional arguments to the om-linux command in task.sh. The customer has a proxy server that is used to access all "external" sites (e.g. pivnet, github, docker hub, etc).

[abbyachau]

@wrast thanks for the information. Prioritised for engineering review

[fredwangwang]

@pivotal-maya-kenedy @calebwashburn please review and prioritize.