Skip to content

Latest commit

 

History

History
1032 lines (774 loc) · 63.7 KB

ChangeLog.md

File metadata and controls

1032 lines (774 loc) · 63.7 KB
Raw

Change Log

Version 10.25.0-Preview-1

Security fixes

  1. Updated version of GoLang used to 1.21 to address security vulnerabilities.

Version 10.24.0

New Features

  1. Print summary logs at lower log levels and add BytesTransferred to the output in the jobs show command. (#1319)
  2. Added a flag --put-blob-size-mb to copy, sync and bench commands to specify the maximum size of a blob to be uploaded using PutBlob. (#2561)
  3. Added support for latest put blob service limits. Block blob put blob size can now be set up to 5000MB. (#2569)
  4. Updated all SDK dependencies to their latest version. (#2599)
  5. Updated summary logs to use consistent wording across all commands. (#2602)

Bug Fixes

  1. Fixed an issue where AzCopy would fail to auto login with the AZCOPY_AUTO_LOGIN_TYPE environment variable set to PSCRED on certain Linux and MacOS environments. (#2491)(#2555)
  2. Fixed a bug where page blob download optimizer would behave incorrectly on highly fragemented blobs if the service times out. (#2445)
  3. Ignore 404 errors on retried deletes. (#2554)
  4. Fixed a bug where the VersionID property would not be honored on the list command. (#2007)
  5. Fixed a bug where ADLS Gen2 paths with encoded special characters would fail to transfer. (#2549)
  6. Fixed an issue where ACL copying would fail when specifying an ADLS Gen2 account with the blob endpoint. (#2546)
  7. Fixed an issue where the snapshot ID would not be preserved when testing which authentication type to use for managed disks. (#2547)
  8. Fixed an issue where copy would panic if a root directory is specified as the destination. (#2036)

Documentation

  1. Removed the azcopy login/logout deprecation notice. (#2589)
  2. Added a warning for customers using Shared Key for Azure Datalake transfers to indicate that Shared Key authentication will be deprecated and removed in a future release. (#2569)
  3. Updated the list help text to clearly indicate the services and authentication types supported.(#2563)

Security fixes

  1. Updated dependencies to address security vulnerabilities.

Version 10.23.0

New Features

  1. Added support to ignore the error and output a summary if a cancelled job has already completed through the use of the --ignore-error-if-completed flag. (#2519)
  2. Added support for high throughput append blob. Append blob block size can now be set to up to 100 MB. (#2480)
  3. Added support to exclude containers when transferring from account to account through the use of the --exclude-container flag. (#2504)

Bug Fixes

  1. Fixed an issue where specifying AZCOPY_AUTO_LOGIN_TYPE in any form other than uppercase would be incorrectly parsed. (#2499)
  2. Fixed an issue where a failure to rename a file from the temporary prefix to the file name would not be considered to be a failed transfer. (#2481)
  3. Fixed an issue where closing the log would panic for benchmark jobs. (#2537)
  4. Fixed an issue where --preserve-posix-properties would not work on download. (#2497)
  5. Fixed an issue where --decompress would not be honored in Linux. (#2392)
  6. Fixed an issue where log files would miss the .log extension. (#2529)
  7. Fixed an issue where AzCopy would fail to set metadata properties on a read only directory when using the --force-if-read-only flag. (#2515)
  8. Fixed an issue where the AzCopy log location on resumed jobs would be reported incorrectly. (#2466)
  9. Fixed an issue with preserving SMB properties in Linux. (#2530)
  10. Fixed an issue where long-running service to service copies using OAuth at the source would result in the token expiring too early. (#2513)
  11. Fixed an issue where AzCopy would try to create folders that already existed, resulting in many unnecessary requests. (#2511)

Documentation

  1. Updated --include-directory-stub inline help to match public documentation. (#2488)

Version 10.22.2

Bug Fixes

  1. Fixed an issue where AzCopy operations pointed at a snapshot or version object would operation on the base object instead.
  2. Fixed an issue where AzCopy would download only the base blob when the --list-of-versions flag was used.

Version 10.22.1

Bug Fixes

  1. Fixed a regression with Azurite support. (#2485)
  2. Fixed an issue where AZCOPY_OAUTH_TOKEN_INFO would be refreshed too often. (#2503)
  3. Fixed an issue where commands would lag for multiple seconds. (#2482)
  4. Fixed an issue where azcopy version would crash. (#2483)

Documentation

  1. Updated documentation to include AZCLI and PSCRED auto login types. (#2494)

Security fixes

  1. Updated dependencies to address security vulnerabilities.

Version 10.22.0

New Features

  1. Migrated to the latest azdatalake SDK.
  2. Added support for OAuth when performing File -> File and Blob -> File copy/sync and File make/list/remove (#2302).
  3. Added support to set tier on premium block blob accounts. (#2337)
  4. Added support to cache latest AzCopy version and check the remote version every 24 hours instead of every run. (#2426)
  5. Updated all SDK dependencies to their latest version and the default service version to 2023-08-03 for all services. (#2402)
  6. Added support to rotate AzCopy logs. (#2213)
  7. Added support to authenticate with Powershell and Azure CLI credentials. (#2433)

Bug Fixes

  1. Fixed an issue where http headers and access tier would sometimes be sent as empty headers.
  2. Fixed an issue where AzCopy would panic when passing an un-parseable URL. (#2404)
  3. Fixed an issue where Object ID would be set as Resource ID when using MSI. (#2395)
  4. Fixed an issue where the percent complete stat could round incorrectly. (#1078)
  5. Fixed an issue where no transfers were scheduled would be logged as an error, it is now logged as a warning. (#874)
  6. Fixed an issue where non canonicalized headers would not be printed in the log. (#2454)
  7. Fixed an issue where cold tier would not be recognized as an allowed tier. (#2447)
  8. Fixed an issue where s2s append blob copies would fail with AppendPositionConditionNotMet error on retry after first experiencing a service timeout error. (#2430)
  9. Fixed an issue where AZCOPY_OAUTH_TOKEN_INFO would not be refreshed. (#2434)

Documentation

  1. Updated --preserve-permissions documentation to indicate the correct roles necessary to perform the operation. (#2440)
  2. Updated help message for sync and copy to include all ADLS Gen2 supported auth methods. (#2440)

Security fixes

  1. Updated dependencies to address security vulnerabilities.

Version 10.22.0-Preview

New Features

  1. Migrated to the latest azdatalake SDK.

Bug Fixes

  1. Fixed an issue where http headers and access tier would sometimes be sent as empty headers.
  2. Fixed an issue where AzCopy would panic when passing an un-parseable URL. (#2404)

Security fixes

  1. Updated dependencies to address security vulnerabilities.

Version 10.21.2

Security fixes

  1. Updated dependencies to address security vulnerabilities.

Version 10.21.1

Bug Fixes

  1. Fixed an issue where validating destination length would fail a job instead of logging the error if read permissions are not provided.

Version 10.21.0

New Features

  1. Migrated to the latest azblob SDK.
  2. Migrated to the latest azfile SDK.
  3. Migrated from deprecated ADAL to MSAL through the latest azidentity SDK.
  4. Added support for sync with Azure Data Lake Storage Gen2. (#2376)

Bug Fixes

  1. Fixed an issue where ACL data would not copy when specifying *.dfs.core.windows.net endpoints (#2347).
  2. Fixed an issue where Sync would incorrectly log that all files, even those that didn't get overwritten, would be overwritten. (#2372)

Documentation

  1. Updated --dry-run documentation to indicate the effects of --overwrite are ignored. (#2325)

Special notes

  1. Due to the migration from ADAL to MSAL, tenant ID must now be set when authorizing with single tenant applications created after 10/15/2018.

Version 10.21.0-Preview

New Features

  1. Migrated to the latest azblob SDK.
  2. Migrated to the latest azfile SDK.
  3. Migrated from deprecated ADAL to MSAL through the latest azidentity SDK.
  4. Deprecated support for object IDs in MSI. Client ID or Resource ID can be used as an alternative.

Special notes

  1. Due to the migration from ADAL to MSAL, tenant ID must now be set when authorizing with single tenant applications created after 10/15/2018.

Version 10.20.1

Bug Fixes

  1. Fixed an issue where LMT data is not returned on list command for Azure Files.

Version 10.20.0

New Features

  1. Mac M1/ARM64 Support
  2. Force small blobs to use PutBlob for any source.
  3. Support to delete CPK encrypted blobs.
  4. Support to follow symlinks when --preserve-smb-permissions is enabled.
  5. Support to return LMT data on list command for Azure Files.

Bug Fixes

  1. Fixed an issue where source trailing dot header was passed when source for a S2S copy is not file service
  2. Gracefully handle File Share trailing dot paths to Windows/Blob (that do not support trailing dot) by skipping such files
  3. Allow trailing dot option to be ignored instead of erroring out in situations it does not apply.
  4. Issue #2186 where AzCopy would panic when using --include-before and --include-after flags on remove file share resources.
  5. Issue #2183 where AzCopy would panic when providing Azure Files URLs with no SAS token.
  6. Fixed a bug where AzCopy would automatically assume a HNS path to be a file if the path did not have a slash terminator.
  7. Fixed an issue where --skip-version-check would not be honored for login, logout, help commands. #2299

Documentation

  1. Add a log for LMTs when a mismatch is encountered.
  2. Added documentation indicating the login and logout commands will be deprecated in the future.

Security fixes

  1. Updated dependencies to address security vulnerabilities.

Version 10.19.0-Preview

New Features

Mac M1/ARM64 Support

Version 10.19.0

New Features

  1. Support for new Cold Tier feature for Azure Blobs (--block-blob-tier=Cold)
  2. Support preserving a trailing dot ('.') in names of files and directories in Azure Files (default is --trailing-dot=Enable)
  3. Alternate modes to preserve hash for hash-based sync (#2214) (default is OS-dependent, either --local-hash-storage-mode=XAttr on MacOS/Linux or --local-hash-storage-mode=AlternateDataStreams on Windows)
    • OS-specific hashing modes are expected to be available on all filesystems the source would traverse. (user_xattr enabled on filesystems on Unix systems, FILE_NAMED_STREAMS flag expected on Windows volumes)
    • HiddenFiles provides an OS-agnostic method to store hash data; to prevent "dirtying" the source, also specify --hash-meta-dir directing AzCopy to store & read hidden hash metadata files elsewhere.
  4. Support 'force-if-readonly' flag for Sync. (false by default)
  5. Preserve posix properties while uploading or downloading from HNS enabled accounts (--preserve-posix-properties, false by default.)

Bug Fixes

  1. Fix situation where large-files would hang infinitely with low value for 'cap-mbps'
  2. Issue #2074 where AzCopy would hang after cancelling
  3. Issue #1888 where directories with empty name are incorrectly handled.
  4. Cancel HNS delete jobs #2117
  5. Fix issue where large chunks could not be scheduled #2228
  6. Fixed segfault on MacOS #1790
  7. Fixed panic on attempt to create AzCopy dir #2191

Version 10.18.1

Bug fixes

  1. Fixed a data race when utilizing hash-based sync. (Issue 2146)
  2. Fixed the destination naming behavior for container-to-container transfers while using --preserve-permissions (Issue 2141)
  3. Temporarily disabled hostname lookup before enumeration (Issue 2144)

Documentation

  1. Modified --from-to flag to be more clear (Issue 2153)

Version 10.18.0

New features

  1. Added support for Content-MD5 in list command. User can now list the MD5 hash of the blobs in the target container.
  2. Added support to resume incomplete blobs. User can now resume the upload of a blob which was interrupted in the middle.
  3. Added support for download of POSIX properties.
  4. Added support for persisting symlink data.

Bug fixes

  1. Fixed Issue 2120
  2. Fixed Issue 2062
  3. Fixed Issue 2046
  4. Fixed Issue 1762

Documentation

  1. Added example for --include-pattern.
  2. Added documentation for --compare-hash.

Security fixes

  1. CPK-related headers are now sanitized from the logs.
  2. Updated dependencies to address security vulnerabilities.

Version 10.17.0

New features

  1. Added support for hash-based sync. AzCopy sync can now take two new flags --compare-hash and --missing-hash-policy=Generate, which which user will be able to transfer only those files which differ in their MD5 hash.

Bug fixes

  1. Fixed issue 1994: Error in calculation of block size
  2. Fixed issue 1957: Repeated Authentication token refresh
  3. Fixed issue 1870: Fixed issue where CPK would not be injected on retries
  4. Fixed issue 1946: Fixed Metadata parsing 5: Fixed issue 1931

Version 10.16.2

Bug Fixes

  1. Fixed an issue where sync would always re-download files as we were comparing against the service LMT, not the SMB LMT
  2. Fixed a crash when copying objects service to service using a user delegation SAS token
  3. Fixed a crash when deleting folders that may have a raw path string

Version 10.16.1

Documentation changes

  1. all was historically an available status option for jobs show but is now documented.

Bug Fixes

  1. Fixed a hard crash when persisting ACLs from remote filesystems on Windows.
  2. Fixed a hard crash when deleting folders containing a % in the name from Azure Files.
  3. Fixed a bug which made Managed Disks data access authentication mode unusable with auto login.

Version 10.16.0

New features

  1. Added time-based flag for remove to include files modified before/after certain date/time.
  2. Added --output-level flag which allows users to set output verbosity.
  3. Added --preserve-posix-properties flag that allows user to persist the results of statx(2)/stat(2) syscall on upload.
  4. Implemented setprops command that allows users to set specific properties of Blobs, BlobFS, and Files.
  5. Implemented multi-auth for managed disks (SAS+OAuth) when the managed disk export account requests it.

Bug fixes

  1. Fixed issue 1506: Added input watcher to resolve issue since job could not be resumed.
  2. Fixed issue 1794: Moved log-level to root.go so log-level arguments do not get ignored.
  3. Fixed issue 1824: Avoid creating .azcopy under HOME if plan/log location is specified elsewhere.
  4. Fixed issue 1830, issue 1412, and issue 873: Improved error message for when AzCopy cannot determine if source is directory.
  5. Fixed issue 1777: Fixed job list to handle respective output-type correctly.
  6. Fixed win64 alignment issue.

Version 10.15.0

New features

  1. Added support for OAuth forwarding when performing Blob -> Blob copy.
  2. Allow users to dynamically change the bandwidth cap via messages through the STDIN.
  3. GCS -> Blob is now GA.
  4. Enable MinIO(S3) logs in DEBUG mode.
  5. Upgraded Go version to 1.17.9.

Bug fixes

  1. Resolved alignment of atomicSuccessfulBytesInActiveFiles.
  2. Fixed issue where last-write-time was still getting persisted even when --preserve-smb-info is false.
  3. Fixed issue where concurrency was always AUTO for Azure Files despite explicit override.
  4. Removed outdated load command following the deprecation of the cflsload package.

Version 10.14.1

Bug fixes

  1. Fixed issue #1625 where a panic occurs during sync scanning.
  2. Fixed remove issue when account has versioning enabled.

Version 10.14.0

New features

  1. Feature to permanently delete soft-deleted snapshots/versions of the blobs has been added (preview). --permanent-delete=none/snapshots/version/snapshotsandversions.
  2. Feature to preserve properties and ACLs when copying to Azure file share root directory.
  3. Pin all APIs to use the default service version 2020-04-08 and let users decide the service version via AZCOPY_DEFAULT_SERVICE_API_VERSION environment variable. Previously, few APIs were not respecting the AZCOPY_DEFAULT_SERVICE_API_VERSION environment variable.

Bug fixes

  1. Fixed issue in which AzCopy failed to copy to classic blob container with preserve blob access tier.
  2. Fixed issue 1630 : AzCopy created extra empty directories at destination while performing S2S transfer from one ADLS Gen2 account to another ADLS Gen2 account.
  3. Changed the way AzCopy was using to obtain and set ACLs to ensure accuracy.
  4. Clarify error message for azcopy sync when source or destination cannot be detected.
  5. Report error when client provided key(CPK) encryption is applied to DFS endpoint.
  6. Fixed issue 1596 : AzCopy failed to transfer files (with '/.' in their path) from AWS S3 to Azure blob storage.
  7. Fixed issue 1474 : AzCopy panicked when trying to re-create an already open plan file.
  8. Improved handling of Auth error against single file.
  9. Fixed issue 1640 : Recursive copy from GCS bucket to Azure container failed with FileIgnored error when using --exclude-path.
  10. Fixed issue 1655 : AzCopy panicked when using --include-before flag.
  11. Fixed issue 1609 : blockid converted to lower case in AzCopy logs.
  12. Fixed issue 1643, issue 1661 : Updated Golang version to 1.16.10 to fix security vulnerabilities in Golang packages.

Version 10.13.0

New features

  1. Added Arc VM support for authorization via managed identity.
  2. Widen managed disk scenario to all md- accounts instead of just md-impexp- accounts.
  3. The concurrency is now set to AUTO for Azure Files by default to avoid throttling.
  4. Decrease the number of create directory calls for Azure Files to avoid throttling.
  5. Added the from-to flag for sync.

Bug fixes

  1. Fixed the memory usage issue with generating the list of skipped/failed transfers in JSON output.
  2. Fixed ADLS Gen2 ACL copying where intermediate folders were missed.
  3. Fixed the S3 to Blob scenario using the login command.
  4. Fixed dry-run for dfs endpoints.
  5. Fixed incorrect percentage-done shown while resuming job.
  6. Fixed login issues on the ARM platforms.
  7. Fixed incorrect progress status for the sync command.
  8. Fixed concurrency map access problem for folder creation tracker.
  9. Fixed resuming with a public source.

Version 10.12.2

Bug fixes

  1. Fix deleting blobs that are of a different type than the specified copy
  2. Fix --delete-destination on Windows download

Version 10.12.1

Bug fixes

  1. Fixed the problem of always receiving overwrite prompt on azure files folders.

Version 10.12.0

Bug fixes

  1. Fixed the problem of always receiving overwrite prompt on azure files folders.

Version 10.12.0

New features

  1. Added support for include and exclude regex flags, which allow pattern matching on the entire paths.
  2. Added dry run mode for copy, remove, and sync. This feature allows the user to visualize the changes before committing them.
  3. For SMB aware locations, preserve-smb-info flag is now true by default.
  4. Improved how folder lmts are obtained to allow time-based filters for folders.
  5. Added support for ACL copying between HNS enabled accounts. The preserve-smb-permissions flag is now deprecated and has been renamed to preserve-permissions.

Bug fixes

  1. Allow from-to to be set for the remove command.
  2. Fixed the problem where resume command did not honor AZCOPY_DEFAULT_SERVICE_API_VERSION.
  3. Fixed the new version check.
  4. Fixed sync issue on Windows where paths are case-insensitive.
  5. Added prompt for invalid characters when importing from S3.
  6. Fixed bug where public S3 buckets cannot be listed.
  7. Sanitize SAS tokens in JSON output for skipped and failed transfers.
  8. Improved folder property preservation across resumes.

Version 10.11.0

New features

  1. Improved performance for copying small blobs (with size less than 256MiB) with Put Blob from URL.
  2. Added mirror mode support in sync operation via mirror-mode flag. The new mode disables last-modified-time based comparisons and overwrites the conflicting files and blobs at the destination if this flag is set to true.
  3. Added flag disable-auto-decoding to avoid automatic decoding of URL-encoded illegal characters when uploading from Windows. These illegal characters could have encoded as a result of downloading them onto Windows which does not support them.
  4. Support custom mime type mapping via environment variable AZCOPY_CONTENT_TYPE_MAP.
  5. Output message on the CLI when AzCopy detects a proxy for each domain.
  6. Interpret DFS endpoints as Blob endpoint automatically when performing service-to-service copy.

Bug fixes

  1. Tolerate enumeration errors for Azure Files and not fail the entire job when a directory is deleted/modified during scanning.
  2. Log skipped transfers to the scanning log.
  3. Fixed pipe upload by adding missing fields such as Metadata, Blob Index Tags, Client Provided Key, Blob Access Tier, etc.
  4. Fixed issue of clean up for the benchmark command.

Version 10.10.0

New features

  1. Support sync for Local/Blob <-> Azure File.
  2. Download to temporary file path (.azDownload-[jobID]-[name]) before renaming to the original path.
  3. Support CPK by name and CPK by value.
  4. Offer knob to disable application logging (Syslog/Windows Event Log).
  5. Trust zonal DNS suffix for OAuth by default.
  6. Added include-directory-stub flag for the copy command, to allow copying of blobs with metadata of hdi_isfolder:true.
  7. Display more fields for the list command, please refer to the help message for example.
  8. Provide environment variable to set request try timeout, to allow faster retries.

Bug fixes

  1. Improve job progress updating mechanism to improve scalability for larger jobs.
  2. Time limit the container creation step, to avoid hanging and improve UX.
  3. Set SMB info/permission again after file upload and copy, to fully preserve the integrity of the permission string and last-write-time.
  4. Fixed module import problem for V10.

Version 10.9.0

New features

  1. Added preview support for importing from GCP Storage to Azure Block Blobs.
  2. Added scanning logs which have low output by default but can become verbose if desired to help in debugging.
  3. Support preservation of tags when copying blobs.
  4. Added last modified time info to the list command.

Bug fixes

  1. Removed unexpected conflict prompt for file share folders with special characters in the name, such as ";".

Version 10.8.0

New features

  1. Added option to disable parallel blob listing
  2. Added support for uploading large files up to 4TiB. Please refer the public documentation for more information
  3. Added support for include-beforeflag. Refer this for more information

Bug fixes

  1. Fixed issue #1246 of security vulnerability in x/text package
  2. Fixed issue share snapshot->share copy with smb permissions

Version 10.7.0

New features

  1. Added support for auto-login when performing data commands(copy/sync/list/make/remove). Please refer to our documentation for more info.
  2. Added blob-tags flag for setting blob index tags when performing copy command. Please note that we support setting blob tags only when tags are explicitly specified. Refer to the public documentations to know more.

Bug fixes

  1. Fixed issue #1139 to preserve content-type in service-to-service transfer.
  2. Fixed issue to allow snapshot restoring.
  3. Fixed issue with setting content-type of an empty file when performing copy command.

Improvements

  1. Added support for setting tier directly at the time of upload API call instead of performing a separate set tier API call.

Version 10.6.1

Bug fixes

  1. Fix issue #971 with scanning directories on a public container
  2. Fix issue with piping where source and destinations were reversed
  3. Allow piping to use OAuth login
  4. Fix issue where transfers with overwrite flag set to IfSourceNewer would work incorrectly
  5. Fix issue #1139, incorrect content type in BlobStorage
  6. Issue #1192, intermittent panic when AzCopy job is abort
  7. Fix issue with auto-detected content types for 0 length files

Version 10.6.0

New features

  1. azcopy sync now supports the persistence of ACLs between supported resources (Azure Files) using the --preserve-smb-permissions flag.
  2. azcopy sync now supports the persistence of SMB property info between supported resources (Azure Files) using the --preserve-smb-info flag. The information that can be preserved is Created Time, Last Write Time and Attributes (e.g. Read Only).
  3. Added support for higher block & blob size
    • For service version 2019-12-12 or higher, the block size can now be less than or equal to 4000 MiB. The maximum size of a block blob therefore can be 190.7 TiB (4000 MiB X 50,000 blocks)
  4. Added support for Blob Versioning
    • Added list-of-versions flag (specifies a file where each version id is listed on a separate line) to download/delete versions of a blob from Azure Storage.
    • Download/Delete a version of blob by directly specifying its version id in the source blob URL.

Bug fixes

  1. Logging input command at ERROR level.

Version 10.5.1

New features

  • Allow more accurate values for job status in jobs commands, e.g. completed with failed or skipped transfers.

Bug fixes

  • Fixed issue with removing blobs with hdi_isfolder=true metadata when the list-of-files flag is used.
  • Manually unfurl symbolic links to fix long file path issue on UNC locations.

Version 10.5.0

New features

  1. Improved scanning performance for most cases by adding support for parallel local and Blob enumeration.
  2. Added download support for the benchmark command.
  3. A new way to quickly copy only files changed after a certain date/time. The copy command now accepts the parameter --include-after. It takes an ISO 8601-formatted date, and will copy only those files that were changed on or after the given date/time. When processing large numbers of files, this is faster than sync or --overwrite=IfSourceNewer. But it does require the user to specify the date to be used. E.g. 2020-08-19T15:04:00Z for a UTC time, 2020-08-19T15:04 for a time in the local timezone of the machine running Azcopy, or 2020-08-19 for midnight (00:00), also in the local timezone.
  4. When detecting content type for common static website files, use the commonly correct values instead of looking them up in the registry.
  5. Allow the remove command to delete blob directory stubs which have metadata hdi_isfolder=true.
  6. The S3 to Blob feature now has GA support.
  7. Added support for load command on Linux based on Microsoft Avere's CLFSLoad extension.
  8. Each job now logs its start time precisely in the log file, using ISO 8601 format. This is useful if you want to use that start date as the --include-after parameter to a later job on the same directory. Look for "ISO 8601 START TIME" in the log.
  9. Stop treating zero-item job as failure, to improve the user experience.
  10. Improved the naming of files being generated in benchmark command, by reversing the digits. Doing so allows the names to not be an alphabetic series, which used to negatively impact the performance on the service side.
  11. Azcopy can now detect when setting a blob tier would be impossible. If azcopy cannot check the destination account type, a new transfer failure status will be set: TierAvailabilityCheckFailure

Bug fixes

  1. Fixed the persistence of last-write-time (as part of SMB info when uploading) for Azure Files. It was using the creation time erroneously.
  2. Fixed the SAS timestamp parsing issue.
  3. Transfers to the File Service with a read-only SAS were failing because we try listing properties for the parent directories. The user experience is improved by ignoring this benign error and try creating parent directories directly.
  4. Fixed issue with mixed SAS and AD authentication in the sync command.
  5. Fixed file creation error on Linux when decompression is turned on.
  6. Fixed issue on Windows for files with extended charset such as [%00 - %19, %0A-%0F, %1A-%1F].
  7. Enabled recovering from unexpectedEOF error.
  8. Fixed issue in which attribute filters does not work if source path contains an asterisk in it.
  9. Fixed issue of unexpected upload destination when uploading a whole drive in Windows (e.g. "D:").

Version 10.4.3

Bug fixes

  1. Fixed bug where AzCopy errored if a filename ended with slash character. (E.g. backslash at end of a Linux filename.)

Version 10.4.2

Bug fixes

  1. Fixed bug in overwrite prompt for folders.

Version 10.4.1

New features

  1. Added overwrite prompt support for folder property transfers.
  2. Perform proxy lookup when the source is S3.

Bug fixes

  1. When downloading from Azure Files to Windows with the --preserve-smb-permissions flag, sometimes the resulting permissions were not correct. This was fixed by limiting the concurrent SetNamedSecurityInfo operations.
  2. Added check to avoid overwriting the file itself when performing copy operations.

Version 10.4

New features

  1. azcopy copy now supports the persistence of ACLs between supported resources (Windows and Azure Files) using the --persist-smb-permissions flag.
  2. azcopy copy now supports the persistence of SMB property info between supported resources (Windows and Azure Files) using the --persist-smb-info flag. The information that can be preserved is Created Time, Last Write Time and Attributes (e.g. Read Only).
  3. AzCopy can now transfer empty folders, and also transfer the properties of folders. This applies when both the source and destination support real folders (Blob Storage does not, because it only supports virtual folders).
  4. On Windows, AzCopy can now activate the special privileges SeBackupPrivilege and SeRestorePrivilege. Most admin-level accounts have these privileges in a deactivated state, as do all members of the "Backup Operators" security group.
    If you run AzCopy as one of those users and supply the new flag --backup, AzCopy will activate the privileges. (Use an elevated command prompt, if running as Admin). At upload time, this allows AzCopy to read files which you wouldn't otherwise have permission to see. At download time, it works with the --preserve-smb-permissions flag to allow preservation of permissions where the Owner is not the user running AzCopy. The --backup flag will report a failure if the privileges cannot be activated.
  5. Status output from AzCopy copy, sync, jobs list, and jobs status now contains information about folders. This includes new properties in the JSON output of copy, sync, list and jobs status commands, when --output-type json is used.
  6. Empty folders are deleted when using azcopy rm on Azure Files.
  7. Snapshots of Azure File Shares are supported, for read-only access, in copy,sync and list. To use, add a sharesnapshot parameter at end of URL for your Azure Files source. Remember to separate it from the existing query string parameters (i.e. the SAS token) with a &. E.g. https://<youraccount>.file.core.windows.net/sharename?st=2020-03-03T20%3A53%3A48Z&se=2020-03-04T20%3A53%3A48Z&sp=rl&sv=2018-03-28&sr=s&sig=REDACTED&sharesnapshot=2020-03-03T20%3A24%3A13.0000000Z
  8. Benchmark mode is now supported for Azure Files and ADLS Gen 2 (in addition to the existing benchmark support for Blob Storage).
  9. A special performance optimization is introduced, but only for NON-recursive cases in this release. An --include-pattern that contains only * wildcards will be performance optimized when querying blob storage without the recursive flag. The section before the first * will be used as a server-side prefix, to filter the search results more efficiently. E.g. --include-pattern abc* will be implemented as a prefix search for "abc". In a more complex example, --include-pattern abc*123, will be implemented as a prefix search for abc, followed by normal filtering for all matches of abc*123. To non-recursively process blobs contained directly in a container or virtual directory include /* at the end of the URL (before the query string). E.g. http://account.blob.core.windows.net/container/*?<SAS>.
  10. The --cap-mbps parameter now parses floating-point numbers. This will allow you to limit your maximum throughput to a fraction of a megabit per second.

Special notes

  1. A more user-friendly error message is returned when an unknown source/destination combination is supplied
  2. AzCopy has upgraded to service revision 2019-02-02. Users targeting local emulators, Azure Stack, or other private/special instances of Azure Storage may need to intentionally downgrade their service revision using the environment variable AZCOPY_DEFAULT_SERVICE_API_VERSION. Prior to this release, the default service revision was 2018-03-28.
  3. For Azure Files to Azure Files transfers, --persist-smb-permissions and --persist-smb-info are available on all OS's. (But for for uploads and downloads, those flags are only available on Windows.)
  4. AzCopy now includes a list of trusted domain suffixes for Azure Active Directory (AAD) authentication. After azcopy login, the resulting token will only be sent to locations that appear in the list. The list is: *.core.windows.net;*.core.chinacloudapi.cn;*.core.cloudapi.de;*.core.usgovcloudapi.net. If necessary, you can add to the the list with the command-line flag: --trusted-microsoft-suffixes. For security, you should only add Microsoft Azure domains.
  5. When transferring over a million files, AzCopy will reduces its progress reporting frequency from every 2 seconds to every 2 minutes.

Breaking changes

  1. To accommodate interfacing with JavaScript programs (and other languages that have similar issue with number precision), all the numbers in the JSON output have been converted to strings (i.e. with quotes around them).
  2. The TransferStatus value SkippedFileAlreadyExists has been renamed SkippedEntityExists and may now be used both for when files are skipped and for when the setting of folder properties is skipped. This affects the input and output of azcopy jobs show and the status values shown in the JSON output format from copy and sync.
  3. The format and content of authentication information messages, in the JSON output format, e.g. "Using OAuth token for authentication" has been changed.

Bug fixes

  1. AzCopy can now overwrite even Read-Only and Hidden files when downloading to Windows. (The read-only case requires the use of the new --force-if-read-only flag.)
  2. Fixed a nil dereference when a prefetching error occurs in a upload
  3. Fixed a nil dereference when attempting to close a log file while log-level is none
  4. AzCopy's scanning of Azure Files sources, for download or Service to Service transfers, is now much faster.
  5. Sources and destinations that are identified by their IPv4 address can now be used. This enables usage with storage emulators. Note that the from-to flag is typically needed when using such sources or destinations. E.g. --from-to BlobLocal if downloading from a blob storage emulator to local disk.
  6. Filenames containing the character : can now safely be downloaded on Windows and uploaded to Azure Files
  7. Objects with names containing + can now safely be used in imported S3 object names
  8. The check-length flag is now exposed in benchmark mode, so that length checking can be turned off for more speed, when benchmarking with small file sizes. (When using large file sizes, the overhead of the length check is insignificant.)
  9. The in-app documentation for Service Principal Authentication has been corrected, to now include the application-id parameter.
  10. ALL filter types are now disallowed when running azcopy rm against ADLS Gen2 endpoints. Previously include/exclude patterns were disallowed, but exclude-path was not. That was incorrect. All should have been disallowed because none (other than include-path) are respected.
  11. Fixed empty page range optimization when uploading Managed Disks. In an edge case, there was previously a risk of data corruption if the user uploaded two different images into the same Managed Disk resource one after the other.

Version 10.3.4

New features

  1. Fixed feature parity issue by adding support for "ifSourceNewer" option on the overwrite flag. It serves as a replacement of the '\XO' flag in V8.

Bug fixes

  1. Fixed jobs clean command on Windows which was previously crashing when the with-status flag was used.

Version 10.3.3

New features

  1. azcopy list is now supported on Azure Files and ADLS Gen 2, in addition to Blob Storage.
  2. The --exclude-path flag is now supported in the sync command.
  3. Added new environment variable AZCOPY_USER_AGENT_PREFIX to allow a prefix to be appended to the user agent strings.

Bug fixes

  1. Content properties (such as Content-Encoding and Cache-Control) are now included when syncing Blob -> Blob and Azure Files -> Azure Files
  2. Custom metadata is now included when syncing Blob -> Blob and Azure Files -> Azure Files
  3. The azcopy list command no longer repeats parts of its output. (Previously it would sometimes repeat itself and show the same blob multiple times in the output.)
  4. The --aad-endpoint parameter is now visible, instead of hidden. It allows use of Azure Active Directory authentication in national clouds (e.g. Azure China).
  5. On Windows, AzCopy now caches information about which proxy server should be used, instead of looking it up every time. This significantly reduces CPU usage when transferring many small files. It also solves a rare bug when transfers got permanently "stuck" with one uncompleted file.
  6. When uploading to a write-only destination, there is now a clearer error message when the built-in file length check fails. The message says how to fix the problem using --check-length=false.
  7. Size checks on managed disk imports are now clearer, and all run at the start of the import process instead of the end.

Version 10.3.2

Bug fixes

  1. Jobs could not be cancelled while scanning was still in progress.
  2. Downloading large managed disks (8 TB and above) failed with errors.
  3. Downloading large page blobs might make no progress for the first 15 or 20 minutes.
  4. There was a rare error where the final output could under-report the total number of files in the job. That error has been fixed.
  5. When using JSON output mode, the output from the rm command on ADLS Gen2 was inconsistent with the output from other commands
  6. After authentication errors, files in progress were not cleaned up (deleted) at the destination. If there was an authentication failure during a job (e.g. a SAS token expired while in use) this could result in files being left behind that had incomplete contents (even though their size looked correct).
  7. The AUTO concurrency option, for automatically tuning concurrency as AzCopy runs, started working too late if scanning (aka enumeration) took a long time. This resulted in reduced throughput when using this setting.
  8. It was not possible to access the root of Windows drives with lowercase drive letters. E.g. d:\
  9. Service to Service transfers would fail when using environment variable to specify OAuth authentication.
  10. Certain errors parsing URLs were not reported clearly.
  11. When downloading to NUL (/dev/null on Linux), files of zero length no longer trigger errors. (Downloads to NUL can be used in performance testing and bulk MD5 checking.

Version 10.3.1

New features

  1. Added helpful deprecation notice for legacy include/exclude flags.
  2. Added back request ID at log level INFO.
  3. Added back cancel-from-stdin option for partner integration.
  4. Added flag to define delete snapshot options for the remove command.

Bug fix

  1. Fixed race condition in shutdown of decompressingWriter.
  2. Made progress reporting more accurate.

Version 10.3.0

Breaking changes

  1. The * character is no longer supported as a wildcard in URLs, except for the two exceptions noted below. It remains supported in local file paths.
    1. The first exception is that /* is still allowed at the very end of the "path" section of a URL. This is illustrated by the difference between these two source URLs: https://account/container/virtual?SAS and https://account/container/virtualDir/*?SAS. The former copies the virtual directory virtualDir by creating a folder of that name at the destination. The latter copies the contents of virtual dir directly into the target without creating a folder named "virtualDir".'
    2. The second exception is when you are transferring multiple whole containers (or S3 buckets). You can use * as a wildcard in the container or bucket name.
  2. The --include and --exclude parameters have been replaced by --include-pattern and --exclude-pattern (for filenames) and --include-path and --exclude-path (for paths, including directory and filenames). The new parameters have behaviour that is better defined in complex situations (such as recursion). The * wildcard is supported in the pattern parameters, but not in the path ones.
  3. There have been two breaking changes to the JSON output that is produced if you request JSON-formatted output. The sync command's output in JSON has changed for consistency reasons, and the final message type, for copy and sync has changed its name from Exit to EndOfJob. Tools using the JSON output format to integrate AzCopy should be aware.
  4. If downloading to "null" on Windows the target must now be named "NUL", according to standard Windows conventions. "/dev/null" remains correct on Linux. (This feature can be used to test throughput or check MD5s without saving the downloaded data.)
  5. The file format of the (still undocumented) --list-of-files parameter is changed. (It remains undocmented because, for simplicity, users are encouraged to use the new --include-pattern and --include-path parameters instead.)

New features

  1. sync is supported from Blob Storage to Blob Storage, and from Azure Files to Azure Files.
  2. copy is supported from Azure Files to Azure Files, and from Blob Storage to Azure Files.
  3. Percent complete is displayed as each job runs.
  4. VHD files are auto-detected as page blobs.
  5. A new benchmark mode allows quick and easy performance benchmarking of your network connection to Blob Storage. Run AzCopy with the parameters bench --help for details. This feature is in Preview status.
  6. The location for AzCopy's "plan" files can be specified with the environment variable AZCOPY_JOB_PLAN_LOCATION. (If you move the plan files and also move the log files using the existing AZCOPY_LOG_LOCATION, then AzCopy will not store anything under your home directory on Linux and MacOS. On Windows AzCopy will keep just one small encrypted file under c:\users\<username>\.azcopy)
  7. Log files and plan files can be cleaned up to save disk space, using AzCopy's new jobs rm and jobs clean commands.
  8. When listing jobs with jobs show, the status of each job is included in the output.
  9. The --overwrite parameter now supports the value of "prompt" to prompt the user on a file-by-file basis. (The old values of true and false are also supported.)
  10. The environment variable AZCOPY_CONCURRENCY_VALUE can now be set to "AUTO". This is expected to be useful for customers with small networks, or those running AzCopy on moderately-powered machines and transfer blobs between accounts. This feature is in preview status.
  11. When uploading from Windows, files can be filtered by Windows-specific file attributes (such as "Archive", "Hidden" etc)
  12. Memory usage can be controlled by setting the new environment variable AZCOPY_BUFFER_GB. Decimal values are supported. Actual usage will be the value specified, plus some overhead.
  13. An extra integrity check has been added: the length of the completed destination file is checked against that of the source.
  14. When downloading, AzCopy can automatically decompress blobs (or Azure Files) that have a Content-Encoding of gzip or deflate. To enable this behaviour, supply the --decompress parameter.
  15. The number of disk files accessed concurrently can be controlled with the new AZCOPY_CONCURRENT_FILES environment variable. This is an advanced setting, which generally should not be modified. It does not affect the number of HTTP connections, which is still controlled by AZCOPY_CONCURRENCY_VALUE.
  16. The values of key environment variables are listed at the start of the log file.
  17. An official Windows 32-bit build is now released, in addition to the usual 64-bit builds for Linux, Mac and Windows.
  18. If you need to refer a literal * in the name of a blob or Azure Files file, e.g. for a blob named "*", escape the * using standard URL escaping. To do this, replace the * with the following character sequence: %2A

Bug fixes

  1. When an AzCopy job is cancelled with CTRL-C, any partially-updated files are now deleted from the destination. Previous releases of AzCopy v10 would just immediately exit, leaving destination files potentially containing an unknown mix of old and new data. E.g. if uploading a new version of a file over top of an old version, cancellation could result in the file being left with some parts containing old data, and some containing new data. This issue affected downloads to local disk and uploads to Azure Files, ADLS Gen 2, page blobs and append blobs. The bug did not affect transfers to block blobs.
  2. If a transfer to a brand-new block blob is cancelled before it completes, the uncommitted blocks are now cleaned up immediately. Previous versions would leave them, for automatic garbage collection to delete 7 days later.
  3. Long pathnames (over 260 characters) are now supported everywhere on Windows, including on UNC shares.
  4. Safety is improved in the rare cases where two source files correspond to just one destination file. This can happen when transferring to a case-insensitive destination, when the new --decompress flag removes an extension but there's already a file without the extension, and in very rare cases related to escaping of filenames with illegal characters. The bug fix ensures that the single resulting file contains data from only one of the source files.
  5. When supplying a --content-type on the command line it's no longer necessary to also specify --no-guess-mime-type.
  6. There is now no hard-coded limit on the number of files that can be processed by the sync command. The number that can be processed (without paging of memory to disk) depends only on the amount of RAM available.
  7. Transfer of sparse page blobs has been improved, so that for many sparse page blobs only the populated pages will transferred. The one exception is blobs which have had a very high number of updates, but which still have significant sparse sections. Those blobs may not be transferred optimally in this release. Handling of such blobs will be improved in a future release.
  8. Accessing root of drive (e.g. d:\) no longer causes an error.
  9. On slow networks, there are no longer excessive log messages sent to the Event Log (Windows) and SysLog (Linux).
  10. If AzCopy can't check whether it's up to date, it will no longer hang. (Previously, it could hang if its version check URL, https://aka.ms/azcopyv10-version-metadata, was unreachable due to network routing restrictions.)
  11. High concurrency values are supported (e.g. over 1000 connections). While these values are seldom needed, they are occasionally useful - e.g. for service-to-service transfer of files around 1 MB in size.
  12. Files skipped due to "overwrite=false" are no longer logged as "failed".
  13. Logging is more concise at the default log level.
  14. Error message text, returned by Blob and File services, is now included in the log.
  15. A log file is created for copy jobs even when there was nothing to copy.
  16. In the log, UPLOAD SUCCESSFUL messages now include the name of the successful file.
  17. Clear error messages are given to show that AzCopy does not currently support Customer-Provided Encryption Keys.
  18. On Windows, downloading a filename with characters not supported by the operating system will result in those characters being URL-encoded to construct a Windows-compatible filename. The encoding process is reversed if the file is uploaded.
  19. Uploading a single file to ADLS Gen 2 works now.
  20. The remove command no longer hangs when removing blobs that have snapshots. Instead it will fail to delete them, and report the failures clearly.
  21. Jobs downloading from ADLS Gen 2 that result in no scheduled transfers will no longer hang.

Version 10.2.1

Bug fix

  1. Fixed outputting error message for SPN login failures.

Version 10.2.0

Bug fix

  1. Security: fixed signature redaction in logs to include all error types: the log entries for network failures and HTTP errors could include SAS tokens. In previous releases, the SAS tokens were not always redacted correctly and could be written to the AzCopy log file and also to the Windows Event Log or the Linux Syslog. Now, SAS tokens are correctly redacted when logging those errors. Note that errors returned by the Storage service itself - such as authentication errors and bad container names – were already redacted correctly.
  2. Added error to using Azure Files without a SAS token (invalid auth configuration).
  3. AzCopy v10 now outputs a sensible error & warning when attempting to authenticate a storage account business-to-business.
  4. --log-level=none now drops no logs, and has a listing in --help.
  5. Fixed bug where piping was not picking up the service version override, making it not work well against Azure Stack.
  6. Fixed a timeout when uploading particularly large files to ADLSG2.
  7. Fixed single wildcard match uploads.

New features

  1. Enabled copying from page/block/append blob to another blob of a different type.
  2. AzCopy now grabs proxy details (sans authentication) from the Windows Registry using mattn/go-ieproxy.
  3. Service Principal Authentication is now available under azcopy login-- check azcopy env for details on client secrets/cert passwords.
  4. SAS tokens are supported on HNS (Hierarchical Namespace/Azure Data Lake Generation 2) Storage Accounts.
  5. Added support for custom headers on ADLS Gen 2.
  6. Added support for fractional block size for copy and sync.
  7. Use different log output for skipped files (so they don't look like failures).
  8. Added bandwidth cap (--cap-mbps) to limit AzCopy's network usage, check azcopy cp -h for details.
  9. Added ADLS Gen2 support for rm command.

Version 10.1.2

Breaking change

  1. Jobs created with earlier releases cannot be resumed with this release. We recommend you update to this release only when you have no partially-completed jobs that you want to resume.

Bug fix

  1. Files with Content-Encoding: gzip are now downloaded in compressed form. Previous versions tried to save a decompressed version of the file. But they incorrectly truncated it at the original compressed length, so the downloaded file was not complete.

    By changing AzCopy to save the compressed version, that problem is solved, and Content-MD5 checks now work for such files. (It is assumed that the Content-MD5 hash is the hash of the compressed file.)

New features

  1. Headers for Content-Disposition, Content-Language and Cache-Control can now be set when uploading files to Blob Storage and to Azure Files. Run azcopy copy --help to see command line parameter information, including those needed to set the new headers.
  2. On-screen job summary is output to the log file at end of job, so that the log will include those summary statistics.

Version 10.1.1

Bug fixes

  1. Fixed typo in local traverser (error handling in walk).
  2. Fixed memory alignment issue for atomic functions on 32 bit system.

Version 10.1.0 (GA)

Breaking changes

  1. The --block-size parameter has been replaced by --block-size-mb. The old parameter took a number of bytes; the new one takes a number of Megabytes (MiB).
  2. The following command line parameters have been renamed, for clarity
    • --output is now --output-type
    • --md5-validation is now called --check-md5
    • --s2s-source-change-validation is now called --s2s-detect-source-changed
    • --s2s-invalid-metadata-handle is is now called --s2s-handle-invalid-metadata
    • --quota (in the make command) is now called --quota-gb. Note that the values were always in GB, the new name simply clarifies that fact

New features

  1. AzCopy is now able to be configured to use older API versions. This enables (limited) support for Azure Stack.
  2. Listing command now shows file sizes.

Bug fixes

  1. AzCopy v10 now works correctly with ADLS Gen 2 folders that contain spaces in their names.
  2. When cancelling with CRTL-C, status of in-progress transfers is now correctly recorded.
  3. For security, the Service-to-Service (S2S) feature will only work if both the source and destination connections are HTTPS.
  4. Use of the --overwrite parameter is clarified in the in-application help.
  5. Fixed incorrect behavior with setting file descriptor limits on platforms including OS X and BSD.
  6. On Linux and OS X, log files are now created with same file permissions as all other files created by AzCopy.
  7. ThirdPartyNotice.txt is updated.
  8. Load DLL in a more secure manner compatible with Go's sysdll registration.
  9. Fixed support for relative paths and shorthands.
  10. Fixed bug in pattern matching for blob download when recursive is off.

Version 10.0.9 (Release Candidate)

Breaking changes

  1. For creating MD5 hashes when uploading, version 10.x now has the OPPOSITE default to version AzCopy 8.x. Specifically, as of version 10.0.9, MD5 hashes are NOT created by default. To create Content-MD5 hashes when uploading, you must now specify --put-md5 on the command line.

New features

  1. Can migrate data directly from Amazon Web Services (AWS). In this high-performance data path the data is read directly from AWS by the Azure Storage service. It does not need to pass through the machine running AzCopy. The copy happens synchronously, so you can see its exact progress.
  2. Can migrate data directly from Azure Files or Azure Blobs (any blob type) to Azure Blobs (any blob type). In this high-performance data path the data is read directly from the source by the Azure Storage service. It does not need to pass through the machine running AzCopy. The copy happens synchronously, so you can see its exact progress.
  3. Sync command prompts with 4 options about deleting unneeded files from the target: Yes, No, All or None. (Deletion only happens if the --delete-destination flag is specified).
  4. Can download to /dev/null. This throws the data away - but is useful for testing raw network performance unconstrained by disk; and also for validating MD5 hashes in bulk (when run in a cloud VM in the same region as the Storage account)

Bug fixes

  1. Fixed memory leak when downloading large files
  2. Fixed performance when downloading a single large file
  3. Fixed bug with "too many open files" on Linux
  4. Fixed memory leak when uploading sparse files (files with big blocks of zeros) to Page Blobs and Azure Files.
  5. Fixed issue where application crashed after being throttled by Azure Storage Service. (The primary fix here is for Page Blobs, but a secondary part of the fix also helps with Block Blobs.)
  6. Fixed functionality and usabilty issues with remove command
  7. Improved performance for short-duration jobs (e.g. those lasting less than a minute)
  8. Prevent unnecessary error message that sometimes appeared when cancelling a job
  9. Various improvements to the online help and error messages.

Version 10.0.8:

  1. Rewrote sync command to eliminate numerous bugs and improve usability (see wiki for details)
  2. Implemented various improvements to memory management
  3. Added MD5 validation support (available options: NoCheck, LogOnly, FailIfDifferent, FailIfDifferentOrMissing)
  4. Added last modified time checks for source to guarantee transfer integrity
  5. Formalized outputs in JSON and elevated the output flag to the root level
  6. Eliminated outputs to STDERR (for new version notifications), which were causing problems for certain CI systems
  7. Improved log format for Windows
  8. Optimized plan file sizes
  9. Improved command line parameter names as follows (to be consistent with naming pattern of other parameters):
    1. fromTo -> from-to
    2. blobType -> blob-type
    3. excludedBlobType -> excluded-blob-type
    4. outputRaw (in "list" command) -> output
    5. stdIn-enable (reserved for internal use) -> stdin-enable