delta/openstack/python-swiftclient.git/tests, branch stable/pike

Add support for versionless endpoints

2017-09-19T07:38:30+00:00

Newer deployments are using versionless Keystone endpoints, and most
OpenStack clients already support this.

This patch enables this for Swift: if an auth_url without any path
component is found, it assumes a versionless endpoint will be used.
In this case the v3 suffix will be appended to the path if none
auth_version is set, and v2.0 is appended if auth_version requires v2.

Closes-Bug: 1554885
Related-Bug: 1691106
Change-Id: If7ecb67776cb77828f93ad8278cc5040015216b7
(cherry picked from commit 2ff3102cf779a507af8fa39296154a17a60f540a)

Allow for uploads from standard input.

2017-07-27T00:04:19+00:00

If "-" is passed in for the source, python-swiftclient will upload
the object by reading the contents of the standard input. The object
name option must be set, as well, and this cannot be used in
conjunction with other files.

This approach stores the entire contents as one object. A follow on
patch will change this behavior to upload from standard input as SLO,
unless the segment size is larger than the content size.

Change-Id: I1a8be6377de06f702e0f336a5a593408ed49be02

Buffer reads from disk

2017-07-12T00:04:49+00:00

Otherwise, Python defaults to 8k reads which seems kinda terrible.

Change-Id: I3160626e947083af487fd1c3cb0aa6a62646527b
Closes-Bug: #1671621

Option to ignore mtime metadata entry.

2017-07-06T17:19:12+00:00

Currently, the swiftclient upload command passes a custom metadata
header for each object (called object-meta-mtime), whose value is
the current UNIX timestamp. When downloading such an object with the
swiftclient, the mtime header is parsed and passed as the atime and
mtime for the newly created file.

There are use-cases where this is not desired, for example when using
tmp or scratch directories in which files older than a specific date
are deleted. This commit provides a boolean option for ignoring the
mtime header.

Change-Id: If60b389aa910c6f1969b999b5d3b6d0940375686

Merge "Skip checksum validation on partial downloads"

2017-06-22T01:13:26+00:00

Merge "Tolerate RFC-compliant ETags"

2017-06-22T01:13:04+00:00

Merge "Stop sending X-Static-Large-Object headers"

2017-06-14T23:35:32+00:00

Merge "Do not set Content-Type to '' with new requests."

2017-06-13T22:07:47+00:00

Do not set Content-Type to '' with new requests.

2017-06-13T17:41:01+00:00

Previously, python-swiftclient worked around a requests issue where
Content-Type could be set to application/x-www-form-urlencoded when
using python3. This issue has been resolved and a fix released in
requests 2.4 (fixed in subsequent releases as well). The patch makes
the workaround conditional on the requests version, so that with
sufficiently new requests libraries, the Content-Type is not set.

For reference, requests 2.4 was released August 29th, 2014. The
specific issue filed in the requests tracker is:
https://github.com/requests/requests/issues/2071.

Related-Change: I035f8b4b9c9ccdc79820b907770a48f86d0343b4
Closes-Bug: #1433767

Change-Id: Ieb2243d2ff5326920a27ce8c3c6f0f5c396701ed

Merge "Fix MockHttpResponse to be more like the Real"

2017-06-12T19:25:45+00:00