API 2.0 Switchover

[petems]

Progress on Switching over to API 2.0 API:

• add-key
• authorize
• create
• destroy
• destroy-image
• droplets
• halt
• help
• images
• info
• info-image
• keys
• password-reset
• rebuild
• regions
• resize
• restart
• sizes
• snapshot
• ssh
• start
• verify
• version
• wait

[petems]

Everything seems to work from my testing, now it's just a matter of getting all the tests ported over.

[zlanich]

I'm no Ruby pro, but I tried this to try out the progress so far and I get an error. Thoughts?:

$ gem build tugboat.gemspec
$ sudo gem install tugboat-2.0.0.pre1.gem
$ tugboat

Error: /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `require': cannot load such file -- tugboat (LoadError)
    from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
    from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:144:in `require'
    from /Library/Ruby/Gems/2.0.0/gems/tugboat-1.0.0/bin/tugboat:8:in `<top (required)>'
    from /usr/bin/tugboat:23:in `load'
    from /usr/bin/tugboat:23:in `<main>'

Update: It seems I successfully installed the gem, but I run into either of the 2 following issues with the executable:

1. If I uninstall the original executable when uninstalling the original tugboat, after installing the APIv2 gem, it doesn't create an exectuable, so "tugboat" isn't found
2. If I leave the original executable there, then install the APIv2 gem, it seems the executable can't find the gem - my assumption is because it's looking for the wrong version of the gem?

Thanks.

[petems]

"This documentation is for version 1 of the DigitalOcean API. It has been deprecated and will be shutdown on Monday, November 9, 2015." Yikes, deadline coming up fast! 😱

[mxdpeep]

yeap, 1 month left...

[FredrikWendt]

This is great progress. Is there an easy way to try this out for a non-Rubyist? I run this all in a docker container and currently run "gem install tugboat", but is there a replacement command which would install this branch instead?
Created a https://www.bountysource.com/issues/8836949-api-2-0-switchover for your efforts so far.

[edanisko]

@FredrikWendt

https://github.com/pearkes/tugboat/blob/master/CONTRIBUTING.md explains a lot about what you are asking.

You're going to wind up doing something similar to the following on a linux command line:

$ sudo apt-get install bundler git
$ cd ~/
$ git clone https://github.com/pearkes/tugboat.git
$ cd tugboat
$ git checkout api2_changes
$ bundle
$ bundle exec rake install #this failed for me but led me to
$ sudo gem install ~/tugboat/pkg/tugboat-2.0.0.pre3.gem

i was able to tugboat authorize and create, tugboat ssh made an ugly fail when i tried to ssh without an id_rsa

but I feel set that I can make the switch on nov 9 without too much pain.

[FreedomBen]

First of all, thank you for your service to the community 😄 .

Do we need to swarm this and get it working with V2? Is it just tests that we're waiting on for a release?

[petems]

Hi @FreedomBen, yeah it's just a matter of getting all the tests moved over to the new job fixtures, cleaning up the commits then doing an official 2.0.0 release. I should have it done before end of October, I've been doing it on and off over the last year, but the deadline has lit a fire and I'm cranking out the last bits of test code. If I don't get the tests finished, I'll release it with pending tests and add a caveat to the post install just in case. Weve had a bunch of people testing the alpha release and most of the commands seem OK 😊

[petems]

PR here: #178

Only 44 failing specs to go! 😄

[petems]

Clean PR here: #180

Just need to figure out why the specs fail peridocially on 2.0.0, then merge soon! 👍

[petems]

Fixed by #183