Added Support Backblaze
Included support to send and receive files to/from Backblaze
I created backblaze account for testing, and added env vars to travis and running now https://travis-ci.org/lytics/cloudstorage
Codecov Report
Merging #62 into master will decrease coverage by
44.41%. The diff coverage isn/a.
@@ Coverage Diff @@
## master #62 +/- ##
===========================================
- Coverage 64.89% 20.48% -44.42%
===========================================
Files 13 13
Lines 1997 1997
===========================================
- Hits 1296 409 -887
- Misses 491 1522 +1031
+ Partials 210 66 -144
| Impacted Files | Coverage Δ | |
|---|---|---|
| awss3/store.go | 0.29% <0%> (-72.92%) |
:arrow_down: |
| azure/store.go | 0.3% <0%> (-69.21%) |
:arrow_down: |
| google/store.go | 0.66% <0%> (-61.88%) |
:arrow_down: |
| sftp/store.go | 13.62% <0%> (-48.04%) |
:arrow_down: |
| google/client.go | 0% <0%> (-31.43%) |
:arrow_down: |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update 2731960...9847dc2. Read the comment docs.
Araddon, your test target does not match the actual code quality :) Could you review it to approve my request? Thank you.
Not entirely sure what is going on with this pr re the import paths? They can't be merged in while pointing to your personal fork. Is your local-directory structure mirroring this github path? ie
/home/dvriesman/go/src/github.com/lytics/cloudstorage
With the cloudstorage .git/config having an upstream pointing to github.com/lytics/cloudstorage and non-upstream pointing at your personal-repo fork?