Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change to droplet_kit for API #250

Open
petems opened this issue Oct 8, 2016 · 2 comments
Open

Change to droplet_kit for API #250

petems opened this issue Oct 8, 2016 · 2 comments
Labels
enhancement refactor

Comments

@petems
Copy link
Owner

petems commented Oct 8, 2016

Right now we haven't kept parity with DigitalOcean's new API features in the API gem we're using Barge (See #249, #248)

At the time we moved, DigitalOcean didn't have a Gem for the API.

Now there is! https://github.com/digitalocean/droplet_kit/

The API for accessing is almost 1:1, plus it's maintained by DO themselves. It would make sense to move over to this so we don't have to implement all the new endpoints in barge.
@petems
Copy link
Owner Author

petems commented Oct 8, 2016

Currently blocked on exposing faraday: digitalocean/droplet_kit#102

@petems petems mentioned this issue Feb 19, 2017
Closed
@petems petems mentioned this issue Mar 6, 2017
Merged
petems added a commit that referenced this issue Jun 22, 2017
@petems
Adding droplet_kit for certain API endpoints
42a599d 
* Initial stage of work for #250
* Key listing and sizes listing is pretty low 
hanging fruit
* The work around searching for nodes is a larger
amount of work, will leave until later.
* Hashie warning fix stolen from 
berkshelf/berkshelf#1668
* Locking `activesupport` gemspec reference 
to allow older rubies to run
* Reverting faraday to older version as pinned
in upstream `droplet_kit`
petems added a commit that referenced this issue Jun 22, 2017
@petems
Adding droplet_kit for certain API endpoints
5349bca 
* Initial stage of work for #250
* Key listing and sizes listing is pretty low 
hanging fruit
* The work around searching for nodes is a larger
amount of work, will leave until later.
* Hashie warning fix stolen from 
berkshelf/berkshelf#1668
* Locking `activesupport` gemspec reference 
to allow older rubies to run
* Reverting faraday to older version as pinned
in upstream `droplet_kit`
petems added a commit that referenced this issue Jun 22, 2017
@petems
Adding droplet_kit for certain API endpoints
cac92ae 
* Initial stage of work for #250
* Key listing and sizes listing is pretty low 
hanging fruit
* The work around searching for nodes is a larger
amount of work, will leave until later.
* Hashie warning fix stolen from 
berkshelf/berkshelf#1668
* Locking `activesupport` gemspec reference 
to allow older rubies to run
* Reverting faraday to older version as pinned
in upstream `droplet_kit`
petems added a commit that referenced this issue Jun 22, 2017
@petems
Adding droplet_kit for certain API endpoints
8371685 
* Initial stage of work for #250
* Key listing and sizes listing is pretty low 
hanging fruit
* The work around searching for nodes is a larger
amount of work, will leave until later.
* Hashie warning fix stolen from 
berkshelf/berkshelf#1668
* Locking `activesupport` gemspec reference 
to allow older rubies to run
* Reverting faraday to older version as pinned
in upstream `droplet_kit`
@petems
Copy link
Owner Author

petems commented Nov 22, 2017

Starting move on some of the larger code blocks with the merge of #284 and the bump to 4.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement refactor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@petems