All VCR cassettes are based off of a non-public API

[jwir3]

Since this originally came out of a project that was private (the Sinking Moon API), we've based all of our API calls on a non-public API. (It's not possible for everyone to access the Sinking Moon API). This means that basically only @jwir3 can recreate the VCR cassettes from scratch.

We should modify this to point to a public API, so that if the need ever arose for others to want to regenerate the API calls in the tests, it can be done.

[jwir3]

Really, what we need to do here is to reorganize all of our specs. It's a complete mess right now. I think a structure like the following might be better:

• with a single environment
  • based off of http
  • GET
  • POST
  • PATCH
  • PUT
  • HEAD
  • DELETE
  • with multiple environments, one based off of http and one based off of HTTPS http`
  • GET (https)
  • POST (https)
  • PATCH (https)
  • PUT (https)
  • HEAD (https)
  • DELETE (https)

This structure would hold for most of our major APIs, then we could test special cases from there in the specifications for config and rest_environment.

[jwir3]

Hmm, actually thinking about this more, we have more than that. We have a matrix of options:

• authenticated vs non-authenticated
• api-key required vs. non-required
• http vs https
• method (GET, POST, PATCH, DELETE, PUT, HEAD)
• multiple vs. single environments
• multiple vs. single APIs

We need to somehow form a combination matrix of the ones that can be specified together and come up with a decent structure in code for the specs.