Merge pull request #10 from cloudinary/v2.0.1-release

V2.0.1 release

Author: achumachenko-cloudinary

CHANGELOG.md

@@ -1,5 +1,13 @@
 # CHANGELOG
 
+[2.0.1] / 2024-02-09
+====================
+
+### Changed
+- Updated outdated dependencies
+- Added hint to the README for monitoring migration errors during execution of the script
+
+
 [2.0.0] / 2023-09-27
 ====================
 

cld-bulk.js

@@ -57,7 +57,7 @@ function configureProgram(program) {
     program
         .name('cld-bulk')
         .description('Extensible CLI tool to efficiently translate CSV file records into Cloudinary API operations')
-        .version('2.0.0');
+        .version('2.0.1');
 }
 
 

package-lock.json

@@ -21,5 +21,5 @@
   "scripts": {
     "test": "jest --verbose"
   },
-  "version": "2.0.0"
+  "version": "2.0.1"
 }

package.json

@@ -32,3 +32,20 @@ node ./cld-bulk.js migrate \
     --output-folder /path/to/output/folder/for/this/migration/round \
     --max-concurrent-uploads 10
 ```
+
+# Monitoring for errors
+
+The migration script keeps updating the `log.json` file in the specified output folder.
+
+Oftentime when errors do occur it is helpful to know what types of errors those are (network "hiccups" or incorrect upload API parameters).
+
+If you would like to monitor for errors in the log file during the script execution you can adjust the following command:
+
+```bash
+#
+# Make sure to replace <input-field-name> with a column name from the input CSV file 
+# (for example, the one you use to pass `public_id` for the asset)
+#
+
+tail -f log.jsonl | jq -r 'select(.summary.status != "MIGRATED") | [.input.<input-field-name>, .summary.status, "--", .summary.err] | join("  ")'
+```