BOSH Release Downloads: CLI and Director Proxy Settings
Locate the release download before changing proxy settings: the CLI host and Director have different outbound environments.
When a release upload by URL fails after the CLI has connected to the Director, inspect where the release is being downloaded. The working CLI-to-Director connection is a different network path.
| Operation | Environment to inspect |
|---|---|
| CLI connects to the Director API | The CLI process |
| Director fetches a supplied release URL | The Director job |
| CLI uploads an already-downloaded local archive | The CLI host for obtaining and uploading that file |
If the Director needs the proxy and the deployment uses the official bosh-deployment repository, incorporate its misc/proxy.yml operations file and required values into the existing Director deployment process. It adds http_proxy, https_proxy and no_proxy to the Director job's environment.
Keep the bypasses required by the Director's internal services; routing external downloads through a proxy should not redirect those internal API calls.
If the CLI host already has an approved working download route, obtaining the release there and uploading the local archive avoids that Director-side fetch. It leaves the Director's policy for later URL downloads unchanged.