Generate test data directly in your storage account.
Configuration
--dirs n : Number of directories to be generated
--files n : Number of files to be generated in each directory
--size n : Size of each file in MBs. 0 will create files with 0 size. Negative value here means file of various sizes upto |n| (0 - n) will be created.
--concurrency n : Number of files being uploaded in parallel
--type [ZERO/RANDOM/FILE] : Type of data to be written in each file.
-- ZERO : File will be filled with zeros
-- RANDOM : File will be filled with random data
-- FILE : Use source file data padded with zeros
--src-file <path> : File path to be used as source data when --type=FILE is set.
--dst-path <path> : Path in the container where test data needs to be generated. By default it will be generated on container root.
--acct-type <type> : As of now only Blob type is supported
--md5 true|false : Compute and set MD5 Sum for each file uploaded to container.
--tier <tier> : Tier to be set for each file uploaded to container.
--delete true|false : Delete previously generated data using this tool
--set-tier true|false : Change tier of previously generated data set. Provie --tier parameter along with this.
--create-stub true|false : Create directory stubs recursively for given path.
--delete-stub true|false : Delete directory stubs recursively for given path.
Environment Variables
AZURE_STORAGE_ACCOUNT : Storage account name
AZURE_STORAGE_ACCESS_KEY : Storage account key
AZURE_STORAGE_SAS_TOKEN : SAS Token for Storage account
AZURE_STORAGE_ACCOUNT_CONTAINER : Container name where generated data will be stored
Example
Before running this command set the environment variables mentioned above and provide your account credentials
Below command generated 100 directories each filled with 100 files each and each file of size 5MB. All this data will be stored in "dir1" in the container and each file will have its md5sum set with blob being in "cool" tier.