Hacker News Reader

Comment by vhbit | Hacker News Reader

CLI isn't mature right now, I'm failing to upload a file, kind of basic functionality.

I had to patch the client to get the authorize_account-command to work (interactively): (ed: lets put that in the righ order, shall we - the dict-key needs two dashes):

    diff -u b2.orig b2
    --- b2.orig     2015-12-17 02:01:55.500314405 +0100
    +++ b2  2015-12-17 02:00:31.032066222 +0100
    @@ -349,7 +349,7 @@

     def authorize_account(args):

    -    auth_urls = {'-production':'https://api.backblaze.com'}
    +    auth_urls = {'--production':'https://api.backblaze.com'}

         option = '--production'
         url = auth_urls[option]

[ed2: quest #182330 "Bug/typo in CLI tool" created -- that's a nasty bugtracker you've got there. Is it possible to just email support somewhere? I get grumpy when I need to run javascript and fill in CAPTCHAs just to file a simple bug ;-) ]

We have chat available :D

IRC?

You can also email b2contact at backblaze.

Yeah, had to do it too, but it's actually fixed, seems both of us are victims of outdated docs as support responded with a link to a neeer version on Github which has this issue solved.

https://github.com/Backblaze/B2_Command_Line_Tool

Yev from Backblaze here -> Interesting. Any specific errors its throwing? You can ping our B2 team directly at -> https://help.backblaze.com/anonymous_requests/new (select B2 product) -> they'll help you debug!

It says "No such bucket" while `b2 list_buckets` sees that bucket. I've filed an issue earlier today (it got to Nathan). I'd be happy to provide any details to fix this.

Interesting! Nathan knows his stuff, he'll get you sorted :)

Same issue over here, any news?

Got no response yet

Nilay here from Backblaze. We changed the API to use bucket name's instead of bucket id's... but the B2 CLI script on our website is out of date.

The version on github is accurate. https://github.com/Backblaze/B2_Command_Line_Tool

Sorry about the confusion.

Yep, I know, see https://news.ycombinator.com/item?id=10749797

I don't have any, but I'm a bit removed from that team. May want to ping them again to see if there's any status updates.

So the issue for me was solved once I started to use bucket name instead of bucket id.

The latter was mentioned in online docs here: https://www.backblaze.com/b2/docs/quick_command_line.html but seems it's REALLY outdated.

Do you have an account?

Reply on news.ycombinator.com