Gsutil

=======================================
Bug Fixes
------------------
- Fixed an issue with the "rsync" command on Windows that would cause gsutil
to incorrectly join file path segments when the source given was the root
of a drive, e.g. "C:".
- Fixed several places where gsutil referenced a variable that had not been
correctly imported.

Other Changes
------------------
- Several documentation updates and clarifications.

=======================================
Bug Fixes
------------------
- Fixed a file path resolution issue on Windows that affected local-to-cloud
copy-based operations ("cp", "mv", "rsync"). If a local file URI containing
relative path components ("." or "..") or forward slashes (rather than
backslashes) was provided as a source argument, the resulting destination
object(s) was incorrectly named. For recursive operations, this resulted in
several files being copied to the same object path, overwriting each other.
- Fixed an issue with the "rsync" command on Windows that resulted in each rsync
invocation not being able to delete its temporary synchronization files on
disk.
- Fixed an issue where reading a specific generation of an object from S3 would
fail.
- Fixed an issue where running gsutil with the top-level "-q" flag would result
in credential-related logging statements being emitted to stderr.
- Gsutil no longer allows copying from streamed input if the top-level "-m" flag
is specified. While this was previously allowed, it did not work correctly.

Other Changes
------------------
- Several documentation updates and clarifications.

=======================================
New features
------------------
- Added support for reauthentication within gsutil. Note that this only affects
authentication when "gs_oauth2_refresh_token" is configured under the
"Credentials" section of the boto config file and that token corresponds to a
user account enrolled in 2-step verification.

Bug Fixes
------------------
- When creating a signed URL via the "signurl" command, gsutil now verifies that
the specified expiration isn't longer than 7 days (the maximum allowed by the
service).
- To support rewriting objects to be encrypted using a bucket's default KMS key,
the "rewrite" command now rewrites all specified objects if no value is
specified for "encryption_key" under the "GSUtil" section in the boto config
file.

Other Changes
------------------
- Several documentation updates and clarifications.

=======================================
New features
------------------
- Added Cloud KMS support for Google Cloud Storage resources, allowing the use
of customer-managed encryption keys (CMEKs). Bucket-related functionality
includes the new "kms" command, which can be used to get or set a bucket's
default KMS key. Concerning objects, users may now specify the CMEK to be used
for encryption via their boto config file, in the "encryption_key" attribute.
In this way, users may specify either a CSEK or a CMEK to encrypt new objects,
but not both. For more information, see "gsutil help encryption".

Other Changes
------------------
- Several documentation updates and clarifications.

=======================================
New features
------------------
- Added transport compression support, available through the "-j" and "-J"
options for the "cp", "mv", and "rsync" commands. This is useful when
uploading files with highly-compressible content. When specificed, files being
uploaded are compressed on-the-fly in memory, sent to GCS, and uncompressed by
GCS before they are stored. See "gsutil help cp" for additional information.
- When "use_magicfile=True" is set in the boto config file, gsutil will now
append the detected charset, if present, to the object's Content-Type metadata
field. For example, a Content-Type might be populated with
"text/html; charset=us-ascii" rather than simply "text/html".

Bug Fixes
------------------
- Improved error handling and logging for upload resumption.
- After encountering a PreconditionException, the "acl ch" command will now
re-fetch the object generation before retrying.
- Fixed issue with parsing lifecycle conditions when using the XML API.
Conditions whose values could be evaluated by Python as "falsy" (e.g. setting
an "age" condition to the number 0 or "isLive" to false) would be omitted from
the lifecycle configuration when "prefer_api=xml" was set in the boto config
file. Note that the JSON API is preferred by default, so most users were
unlikely to encounter this issue.
- For commands that fetch bucket ACLs or default ACLs, when the user does not
have storage.buckets.getIamPolicy on the GCS bucket, using the XML API will
now behave consistently with the JSON API and display ACL/default ACL fields
as empty, rather than throwing a CommandException.

Other Changes
------------------
- Several documentation updates and clarifications.
- The "signurl" command now uses signature V4 signing format to generate URLs.

=======================================
New features
------------------
- Added newest version of the Boto library, which includes support for using
Signature Version 4 to connect to S3 buckets via the "use-sigv4 = True" and
"host = s3.<region>.amazonaws.com" Boto options under the "[s3]" section.
- Added support for Requester Pays functionality when making requests to GCS
buckets with this feature enabled. For example usage, see the entry for "-u"
in "gsutil help options". Requester Pays is currently only supported for
requests using the GCS JSON API; XML API support will be added in a later
version.

Bug Fixes
------------------
- Fixed issue where attempting to preserve ACLs by using "-p" with cp/mv/rsync
would fail when the destination is a local file.
- Improved quality of several ambiguous error messages.

Other Changes
------------------
- The proxy_rdns option is now True by default when a proxy is set. Also added
Boto config file comments explaining that gcloud proxy options, if present,
take precedence over corresponding Boto settings and environment variable
settings.
- Following the deprecation of Python 2.6 support for gsutil, code sections that
were only present to support Python 2.6 have been removed.
- Several documentation updates and clarifications.