I started this project because I had another project that needed to upload files straight to Backblaze B2 object storage. I guess you could instead use the S3 GitHub Action and point it at your Backblaze bucket, but I guess I forgot and figured I could solve it natively.
I forked Wilson’s B2-setup Action, figuring I could apply another layer to then upload the file based on arguments to save a bunch of effort because Wilson had already figured out how to get the B2 CLI working on all OS available in GitHub Actions. I ran in to a few problems however.
One was that Wilson’s B2-setup action does not have a license. Meaning it was copyrighted and I had concerns about extending the code base. I almost started again and built my action using Docker but I still worked in the fork, which looks weird if you look at the commit history
The other issue was I had difficulties getting the input arguments to work and the project needed npm dependencies built in to the package and it was all starting to get complicated. Which is when I decided to use the cURL Action as inspiration switch to Docker.
I suspect Docker runs are slower as it looks like it builds the docker image before running, it also only runs on the Linux images, but it works, so that’s what I’ve got for now.
I released a V4 based upon the release cycle from Wilson’s code, but then when adding the action to the marketplace I had to create a new release as I couldn’t work out how to delete the v4 tag in the GitHub interface. So for no reason v4 isn’t used and v5, which is identical is the published version.
I am very pleased with the icon.
I licenced this one under AGPLv3, unlike my other GitHub action. I was reminded of the purpose of AGPLv3 and in the case of an Action I would expect it only mattered if someone changed this action for some reason.