@azure-tools/azcopy-node v3.4.2
AzCopy Node
This package allows you to invoke AzCopy v10 from NodeJS.
Basic Usage
const { AzCopyClient } = require("@azure-tools/azcopy-node");
let client = new AzCopyClient();
// AzCopy is used to move things from one location to another.
let src = /* a `AzCopyLocation` */;
let dst = /* a `AzCopyLocation` */;
// All functions that start AzCopy jobs return a job ID.
let jobId = await client.copy(src, dst);
let status;
// You use this job ID to check on the progress of your job, and know if it has finished.
while (!status || status.StatusType !== "EndOfJob") {
    let jobInfo = await copyClient.getJobInfo(jobId)
    status = jobInfo.latestStatus;
    await new Promise((resolve, reject) => setTimeout(resolve, 1000));
}Where to Find an AzCopy Executable
AzCopy executables are available on NPM for Windows (32 and 64 bit), macOS, and Linux. This package already declares each of these as optional dependencies. The exact packages are:
- @azure-tools/azcopy-win32
- @azure-tools/azcopy-win64
- @azure-tools/azcopy-linux
- @azure-tools/azcopy-darwin
They are optional dependencies because each package declares itself to only be valid for the OS it is intended for. This means that when you run npm install that only the AzCopy executable for the OS you are currently on will be installed.
If you wish to install all versions you can use the --force flag with npm install.
Specifying What AzCopy Executable to Use
By default, AzCopyClient will use the @azure-tools AzCopy executable package which best matches your OS and architecture. There are two possibilities for using a different executable:
- Using a different architecture of @azure-tools AzCopy executable package (bit-ness) if available
- Using a custom AzCopy executable
For the first scenario, if you want to force run either the 32bit for 64bit executable you can specify a bitness in the options object for the AzCopyClient constructor. Since Windows is the only OS to offer both 32 and 64 bit executables, this is really only something to consider for Windows.
For the second scenario you can use the exe field in the options object for the AzCopyClient constructor to specify the path to a custom AzCopy executable. If you do this there are two things to be aware of:
1. This package is verified against a specific version of AzCopy. It is not recommended to use a different version than that. If you decide to do so, make sure to test and verify appropriately.
2. When using a IRemoteAuthLocation, you cannot use the non-NPM versions of AzCopy on Linux. The AzCopy in @azure-tools/azcopy-linux uses a special build of AzCopy.
Azure AD Scenarios
When you use an IRemoteAuthLocation, azcopy-node must share the authentication/refresh token included in that location with the running AzCopy executable. This is done via the OS credential store. It is up to you to implement an ICredentialStore and include it in the options for your AzCopyClient if you wish for this to happen.
new AzCopyClient({
    credentialStore: {
        setEntry: async (service: string, account: string, value: string, exePath?: string, description?: string): Promise<void> => {
            // you implement this
        },
        getEntry: async (service: string, account: string): Promise<string | null> => {
            // you implement this
        },
        deleteEntry: async (service: string, account: string): Promise<boolean> => {
            // you implement this
        }
    }
});More information can be found in the JSDoc comments for ICredentialStore and TokenRefresher.
chmod
On macOS and Linux you may need to chmod the executables in order for them to run.
Change Log
3.2.0
- Validated against AzCopy 10.23.0.
3.1.0
- Validated against AzCopy 10.22.2.
- Added getCliCommandmethod onAzCopyClient.
3.0.0
- Added macOS ARM64 AzCopy as a dependency.
- Added trailingDottoICommonOptions.
- Removed BitnessfromIAzCopyClientOptions.
- Updated functions for getting available AzCopy executables.
2.12.0
- Validated against AzCopy 10.18.1
- Add "Cold" as supported block blob tier in ICopyOptions.
2.11.0
- Validated against AzCopy 10.17.0
- Improved comments for listOfFilesandlistOfVersionsinICommonOptions.
2.10.1
- Added "FileBlob"and"BlobFile"toFromToOption
2.10.0
- Added preserveBlobTagstoICopyOptions
2.9.0
- Added jobsRemovemethod onAzCopyClient
2.8.0
- Validated against AzCopy 10.16.2
- Added "FileFiletoFromToOption
- Added includeRegextoICopyOptions
- Added asSubDirtoICopyOptions
- Added several new types for convenience:- OverwriteExistingOptionfor use in- ICopyOptions
- AccessTierfor use in- ICopyOptions
- RemoteAzCopyLocationunion of all remote locations
 
2.7.0
- Validated against AzCopy 10.16.0
- Added a deleteJobmethod toAzCopyClient. Use this function to save memory once a job's info/status is no longer needed.
- Added support for changing bandwidth dynamically. Support includes:- Addition of nextPerformanceAdjustmentTimetoIJobInfo
- Addition of adjustCapMbpsmethod onAzCopyClient
 
- Addition of 
2.6.0
- Validated against AzCopy 10.14.1.
2.5.0
- Validated against AzCopy 10.13.0.
2.4.0
- Validated against AzCopy 10.12.2
- Added includeDirectoryStubtoICopyOptions
- Fixed --trusted-microsoft-suffixesbeing added to commands whentrustedDomainSuffixesis an empty array.
2.3.0
- Validated against AzCopy 10.11.0
- Options common to both ICopyOptionsandIDeleteOptionswere moved a new interface,ICommonOptions, withICopyOptionsandIDeleteOptionseach inheriting that interface.
- Added includePathtoICopyOptionsandIDeleteOptions.
- Added logLeveltoICopyOptionsandIDeleteOptions.
- Added disableAutoDecodingtoICopyOptions.
- Added cacheControltoICopyOptions.
2.2.0
- Validated against AzCopy 10.10.0.
- Added blockSizeMbtoICopyOptions.
- Added trustedDomainSuffixestoICopyOptionsandIDeleteOptions.
2.1.0
- Validated against AzCopy 10.9.0.
2.0.0
- Validated against AzCopy 10.8.0.
- Breaking Change! This package no longer directly depends on keytarormacos-keychain. If you want to use anIRemoteAuthLocationyou must now implement anICredentialStoreand include it in the options for yourAzCopyClient. See Azure AD Scenarios and the JSDoc comments inICredentialStoreandTokenRefresherfor more information.
- All remote locations now include an optional versionId. This can be used to point at a blob version.
- Added listOfVersionstoICopyOptionsandIDeleteOptions. Works similarly tolistOfFiles. See the JSDoc comments in either of the options files for more details.
- Added "Archive"as a possible value of theaccessTiercopy option.
- Added forceIfReadOnlytoIDeleteOptions.
- Added tagstoICopyOptions.
1.0.0
- First version of this package!
- Validated against AzCopy 10.5.0.