Skip to content

Conversation

@jdickey
Copy link
Owner

@jdickey jdickey commented Jul 24, 2017

Second item on the list in Issue #1, supporting CLI usage as specified in the documentation for the All Droplets command.

Some lights that should have come on years ago are slowly flickering to life; maybe we can burn this bike-shed down one of these days.

jdickey added 19 commits July 19, 2017 13:26
This required that the `terminal-table` Gem be added to the Gemspec.
DataRequest simply returned the unparsed JSON string retrieved via the API, without parsing it into an object with `#body` and `#status` readers. We had a test-focus line inadvertently left in that prevented us from seeing this, and several other problems. Fixes continuing.
This shadows the existing $DO_API_TOKEN environment variable; the next commit will switch to using it instead of accessing `ENV['DO_API_TOKEN']` directly.

Why, you ask? Using  this *should* let Just Anyone™ clone the repo while keeping secure data secure; a commented-out "definition" suggests a way forward to the incompletely-knowledgeable user.
Also a mild refactoring/cleanup.
Defaulting to non-stubbed, obviously.

Also eliminate `api_token` parameter, since it's now retrieved from Chamber or environment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants