Backblaze B2 support

[matvp91]

This ticket tracks support for Backblaze B2.

Bugs:

• package Job failed with error: Unsupported value for canned acl 'public-read' #150
• package job fails with error: "CPU too busy" #151

Features:

• Allow ACL to be set by the package job input payload. #152

[matvp91]

@insanity54, I've closed #151 as concurrency fixes the issue.

Know that I'm about to drop s3-sync-client in favor of a custom implementation, allowing us finer grained control of how uploads are managed. The goal is to have a looser retry mechanism in place, a job shall stay in progress longer while it's waiting for a retry (exponential backoff) or when it's busy retrying. I think the work in #169 should fix your previously reported issues in a nicer way.

Once that's completed, would you be willing to check if your own retry logic is no longer necessary?

[matvp91]

@insanity54, anything else you bumped into with B2? If not, I'll close this issue soon.

[insanity54]

I'm using 1.2.0 (docker :latest tag). It's working well! I did run into the error, Unsupported value for canned acl 'public-read' again, but that was because I forgot to set public: false on the input.

Example:

{
  assetId: "ca6397ec-d296-4332-8de3-143d82c3b828"
  concurrency: 5
  language: "english"
  name: "hls"
  public: true
}

After I set public: false it was succeeding. All good with B2 now.

[matvp91]

Thank you for the info! I'll close this one.