Explicitly assign status (& operation)

[achumachenko-cloudinary]

          Having "MIGRATED' as the default feels risky to me.

Should this not be set after we have the response?

I see there being 4 status':

• MIGRATED = New upload of an asset
• OVERWRITTEN = Public id already existed and overwrite was set to true (overwritten is in the response object)
• ALREADY EXISTED = Public id already existed and overwrite was set to false (existing is in the response object)
• FAILED = Error occurred

Originally posted by @mgriff in #7 (comment)

[achumachenko-cloudinary]

Initially the tool had been designed for migration flow only.
Now we change the context to allow for any bulk operations.

I think to "support" this context the main loop would need to support the following scenarios:

Have the summary.status set to 'NA'

• API call succeeds
  • Assign the summary.status to 'OK'
  • Run a custom function (passed to the loop) that takes in API response object and returns "sub-status". Migration would have the four. But then in context of, let's say, bulk metadata updates the "sub-status" may be different
• API call fails
  • Assign the summary.status to 'ERR'

This will allow to identify records with summary.status set to 'NA' (indicating an anomaly) as well as filter the report for those OK/ERR values. The "sub-status" (name to be determined) field can then be used for further filtering depending on the reporting needs.