A .boto Proxy Profile for an Existing gsutil Job

Set the Boto proxy fields and load shared routing configuration alongside a user's existing gsutil configuration.

A workflow that still uses the legacy gsutil CLI can configure its proxy in the [Boto] section of the boto configuration:

[Boto]
proxy = proxy.example.net
proxy_port = 8080
proxy_type = http

The host field contains the hostname, while the port and protocol have their own fields. This is gsutil's documented configuration format, rather than a complete proxy URI placed into the host field. For an allowed public-service test, an HTTP address from the HTTP proxy list can fill the endpoint fields only when none of the loaded BOTO_PATH files supplies proxy_user or proxy_pass.

The configuration can live in the user's existing .boto file. For a shared deployment profile, gsutil also supports BOTO_PATH, which lists files to load in order. On a Unix system, an example is:

export BOTO_PATH=/etc/team/gsutil-proxy.cfg:$HOME/.boto

The first file can hold team-wide routing defaults, while the user's existing file keeps personal configuration. Use semicolons as the path delimiter on Windows.

The documented fields also include proxy_user, proxy_pass and proxy_rdns for applicable proxy setups. Set the profile for the account running the gsutil job, and keep the file order deliberate when more than one file defines the same option.

Winndannde jowitiiɗe heen