Tag for 1.4.0 release

Author: alfpark

CHANGELOG.md

@@ -2,6 +2,28 @@
 
 ## [Unreleased]
 
+## [1.4.0] - 2018-08-08
+### Added
+- Azure Storage URL support for the CLI via `--storage-url` and
+`--sync-copy-dest-storage-url` ([#79](https://github.com/Azure/blobxfer/issues/79)).
+Please see the usage docs for more information.
+- `--restore-file-lmt` option for download operations
+([#82](https://github.com/Azure/blobxfer/issues/82)). Please see the usage
+docs for more information.
+
+### Changed
+- **Breaking Change**: `restore_file_attributes` boolean property under
+`download` has been replaced with `restore_file_properties` map containing
+`attributes` and `lmt` for YAML configurations. This change was done to
+provide consistency with the `store_file_properties` map under `upload`.
+Please see the YAML configuration doc for more information.
+- Updated dependencies
+
+### Fixed
+- Fix and improve SAS handling to limit functionality based on SAS token
+scope and permissions ([#80](https://github.com/Azure/blobxfer/issues/80)).
+Please see the usage and limitations docs for more information.
+
 ## [1.3.1] - 2018-06-29
 ### Changed
 - Updated dependencies
@@ -371,7 +393,8 @@ usage documentation carefully when upgrading from 0.12.1.
   `--no-skiponmatch`.
 - 0.8.2: performance regression fixes
 
-[Unreleased]: https://github.com/Azure/blobxfer/compare/1.3.1...HEAD
+[Unreleased]: https://github.com/Azure/blobxfer/compare/1.4.0...HEAD
+[1.4.0]: https://github.com/Azure/blobxfer/compare/1.3.1...1.4.0
 [1.3.1]: https://github.com/Azure/blobxfer/compare/1.3.0...1.3.1
 [1.3.0]: https://github.com/Azure/blobxfer/compare/1.2.1...1.3.0
 [1.2.1]: https://github.com/Azure/blobxfer/compare/1.2.0...1.2.1

blobxfer/operations/progress.py

@@ -200,7 +200,7 @@ def output_parameters(general_options, spec):
             spec.options.strip_components))
         log.append('         compute file md5: {}'.format(
             spec.options.check_file_md5))
-        log.append('                  restore: attr={} lmt={}'.format(
+        log.append('       restore properties: attr={} lmt={}'.format(
             spec.options.restore_file_properties.attributes,
             spec.options.restore_file_properties.lmt))
         log.append('          rsa private key: {}'.format(

blobxfer/version.py

@@ -22,4 +22,4 @@
 # FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
 # DEALINGS IN THE SOFTWARE.
 
-__version__ = '1.3.1'
+__version__ = '1.4.0'

docs/99-current-limitations.md

@@ -3,18 +3,19 @@ Please read this section carefully for any current known limitations to
 `blobxfer`.
 
 ### SAS Keys (Tokens)
-* `blobxfer` is fundamentally limited in what operations it can perform
+`blobxfer` is fundamentally limited in what operations it can perform
 if given a restricted scope SAS token. This is not a limitation with
 `blobxfer` itself, but with the permissions that are granted by the SAS
 token. The following are a few examples:
-    * Containers or file shares cannot be created if not given an
-      account-level SAS with the appropriate signed resource type.
-    * Objects cannot be listed within a container or file share if not given
-      an account-level SAS or a container-level object SAS. If a
-      non-container object-level SAS is provided, remote
-      paths associated with these SAS tokens must be a single entity.
-    * Non-download skip-on processing cannot be performed for SAS tokens
-      without sufficient read permission.
+
+* Containers or file shares cannot be created if not given an
+  account-level SAS with the appropriate signed resource type.
+* Objects cannot be listed within a container or file share if not given
+  an account-level SAS or a container-level object SAS. If a
+  non-container object-level SAS is provided, remote
+  paths associated with these SAS tokens must be a single entity.
+* Non-download skip-on processing cannot be performed for SAS tokens
+  without sufficient read permission.
 
 ### Client-side Encryption
 * Client-side encryption is currently only available for block blobs and