Source: azure-storage-azcopy
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Uploaders: jpiotrowski <TODO>
Section: golang
Testsuite: autopkgtest-pkg-go
Priority: optional
Build-Depends: debhelper-compat (= 13),
               dh-golang,
               golang-any,
               golang-github-azure-azure-pipeline-go-dev,
               golang-github-azure-azure-storage-blob-go-dev,
               golang-github-azure-azure-storage-file-go-dev,
               golang-github-azure-go-autorest-dev,
               golang-github-golang-groupcache-dev,
               golang-github-google-uuid-dev,
               golang-github-jeffreyrichter-enum-dev,
               golang-github-mattn-go-ieproxy-dev,
               golang-github-minio-minio-go-dev,
               golang-github-pkg-errors-dev,
               golang-github-spf13-cobra-dev,
               golang-github-wastore-keyctl-dev,
               golang-golang-x-crypto-dev,
               golang-golang-x-oauth2-google-dev,
               golang-golang-x-sync-dev,
               golang-google-api-dev,
               golang-google-cloud-dev,
               golang-gopkg-check.v1-dev
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/go-team/packages/azure-storage-azcopy
Vcs-Git: https://salsa.debian.org/go-team/packages/azure-storage-azcopy.git
Homepage: https://github.com/Azure/azure-storage-azcopy
Rules-Requires-Root: no
XS-Go-Import-Path: github.com/Azure/azure-storage-azcopy

Package: azure-storage-azcopy
Architecture: any
Depends: ${misc:Depends},
         ${shlibs:Depends}
Built-Using: ${misc:Built-Using}
Description: The new Azure Storage data transfer utility - AzCopy v10 (program)
 AzCopy v10 AzCopy v10 is a command-line utility that you can use to copy
 data to and from containers and file shares in Azure Storage accounts.
 AzCopy V10 presents easy-to-use commands that are optimized for high
 performance and throughput.  Features and capabilities :whitecheckmark:
 Use with storage accounts that have a hierarchical namespace (Azure Data
 Lake Storage Gen2).
 .
 :whitecheckmark: Create containers and file shares.
 .
 :whitecheckmark: Upload files and directories.
 .
 :whitecheckmark: Download files and directories.
 .
 :whitecheckmark: Copy containers, directories and blobs between storage
 accounts (Service to Service).
 .
 :whitecheckmark: Synchronize data between Local <=> Blob Storage, Blob
 Storage <=> File Storage, and Local <=> File Storage.
 .
 :whitecheckmark: Delete blobs or files from an Azure storage account
 .
 :whitecheckmark: Copy objects, directories, and buckets from Amazon Web
 Services (AWS) to Azure Blob Storage (Blobs only).
 .
 :whitecheckmark: Copy objects, directories, and buckets from Google
 Cloud Platform (GCP) to Azure Blob Storage (Blobs only).
 .
 :whitecheckmark: List files in a container.
 .
 :whitecheckmark: Recover from failures by restarting
 previous jobs.  Download AzCopy The latest binary for
 AzCopy along with installation instructions may be found here
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10).
 Find help For complete guidance, visit any of these articles on the
 docs.microsoft.com website.
 .
 :eightspokedasterisk: Get started with AzCopy (download links here)
 (https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-v10)
 .
 :eightspokedasterisk: Upload files to Azure Blob storage by using AzCopy
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-upload)
 .
 :eightspokedasterisk: Download blobs
 from Azure Blob storage by using AzCopy
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-download)
 .
 :eightspokedasterisk: Copy blobs between
 Azure storage accounts by using AzCopy
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-copy)
 .
 :eightspokedasterisk: Synchronize between Local File System/Azure
 Blob Storage (Gen1)/Azure File Storage by using AzCopy
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-synchronize)
 .
 :eightspokedasterisk: Transfer data with AzCopy and file storage
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-files)
 .
 :eightspokedasterisk: Transfer data with AzCopy and Amazon S3 buckets
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-s3)
 .
 :eightspokedasterisk: Transfer data with AzCopy and Google GCP buckets
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-google-cloud)
 .
 :eightspokedasterisk: Use data transfer tools in Azure Stack Hub Storage
 (https://docs.microsoft.com/en-us/azure-stack/user/azure-stack-storage-transfer)
 .
 :eightspokedasterisk: Configure, optimize, and troubleshoot AzCopy
 (https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-configure)
 .
 :eightspokedasterisk: AzCopy WiKi
 (https://github.com/Azure/azure-storage-azcopy/wiki) Supported Operations
 The general format of the AzCopy commands is: azcopy [command] [arguments]
 --[flag-name]=[flag-value] • bench - Runs a performance benchmark by
 uploading or downloading test data to or from a specified destination•
 copy - Copies source data to a destination location. The supported
 directions are: • Local File System <-> Azure Blob (SAS or OAuth
 authentication)• Local File System <-> Azure Files (Share/directory SAS
 authentication)• Local File System <-> Azure Data Lake Storage (ADLS
 Gen2) (SAS, OAuth, or SharedKey authentication)• Azure Blob (SAS or
 public) -> Azure Blob (SAS or OAuth authentication)• Azure Blob (SAS or
 public) -> Azure Files (SAS)• Azure Files (SAS) -> Azure Files (SAS)•
 Azure Files (SAS) -> Azure Blob (SAS or OAuth authentication)• AWS S3
 (Access Key) -> Azure Block Blob (SAS or OAuth authentication)• Google
 Cloud Storage (Service Account Key) -> Azure Block Blob (SAS or OAuth
 authentication) [Preview]• sync - Replicate source to the destination
 location. The supported directions are: • Local File System <-> Azure
 Blob (SAS or OAuth authentication)• Local File System <-> Azure Files
 (Share/directory SAS authentication)• Azure Blob (SAS or public) ->
 Azure Files (SAS)• login - Log in to Azure Active Directory (AD)
 to access Azure Storage resources.• logout - Log out to terminate
 access to Azure Storage resources.• list - List the entities in a
 given resource• doc - Generates documentation for the tool in Markdown
 format• env - Shows the environment variables that you can use to
 configure the behavior of AzCopy.• help - Help about any command• jobs
 - Sub-commands related to managing jobs• load - Sub-commands related
 to transferring data in specific formats• make - Create a container
 or file share.• remove - Delete blobs or files from an Azure storage
 accountFind help from your command prompt For convenience, consider
 adding the AzCopy directory location to your system path for ease of
 use. That way you can type azcopy from any directory on your system.
 .
 To see a list of commands, type azcopy -h and then press the ENTER key.
 .
 To learn about a specific command, just include the name of the command
 (For example: azcopy list -h).
 .
 AzCopy command help example
 .
 If you choose not to add AzCopy to your path, you'll have to change
 directories to the location of your AzCopy executable and type azcopy
 or .\azcopy in Windows PowerShell command prompts.  Frequently asked
 questionsWhat is the difference between sync and copy?• The copy
 command is a simple transferring operation. It scans/enumerates the
 source and attempts to transfer every single file/blob present on the
 source to the destination.  The supported source/destination pairs
 are listed in the help message of the tool.• On the other hand,
 sync scans/enumerates both the source, and the destination to find
 the incremental change.  It makes sure that whatever is present in
 the source will be replicated to the destination. For sync,• If your
 goal is to simply move some files, then copy is definitely the right
 command, since it offers much better performance.  If the use case
 is to incrementally transfer data (files present only on source) then
 sync is the better choice, since only the modified/missing files will
 be transferred.  Since sync enumerates both source and destination to
 find the incremental change, it is relatively slower as compared to
 copyWill copy overwrite my files?  By default, AzCopy will overwrite
 the files at the destination if they already exist. To avoid this
 behavior, please use the flag --overwrite=false.  Will sync overwrite
 my files?  By default, AzCopy sync use last-modified-time to determine
 whether to transfer the same file present at both the source, and
 the destination.  i.e, If the source file is newer compared to the
 destination file, we overwrite the destination You can change this
 default behaviour and overwrite files at the destination by using the
 flag --mirror-mode=true Will 'sync' delete files in the destination
 if they no longer exist in the source location?  By default, the
 'sync' command doesn't delete files in the destination unless you use
 an optional flag with the command.  To learn more, see Synchronize files
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-synchronize).
 How to contribute to AzCopy v10 This project welcomes contributions and
 suggestions.  Most contributions require you to agree to a Contributor
 License Agreement (CLA) declaring that you have the right to, and
 actually do, grant us the rights to use your contribution. For details,
 visit https://cla.microsoft.com.
 .
 When you submit a pull request, a CLA-bot will automatically determine
 whether you need to provide a CLA and decorate the PR appropriately
 (e.g., label, comment). Simply follow the instructions provided by the
 bot. You will only need to do this once across all repos using our CLA.
 .
 This project has adopted the Microsoft Open Source Code of
 Conduct (https://opensource.microsoft.com/codeofconduct/).
 For more information see the Code of Conduct FAQ
 (https://opensource.microsoft.com/codeofconduct/faq/) or contact
 opencode@microsoft.com (mailto:opencode@microsoft.com) with any additional
 questions or comments.
