options.auth passes straight through to request library.

[Freyert]

The reason to do this is so that we don't re-do the functionality that request has already made for us. This way users can use OAuth Tokens or any other authentication strategy supported by request, but still remains backwards compatible with the cradle API.

I'm in the midst of providing a request pass through option to open cradle up to the full functionality. Configuration in general could use a re-work, but would definitely lead to breaking changes in most areas. In my opinion, 90% of cradle's configuration variables configure request and therefore cradle should pick off the values it needs and just pass the rest to request.

[panuhorsmalahti]

Do you consider this to be a breaking change? If not, I can merge this for the next release (which I should do asap). After that we can start working on 1.0.0 with reasonable breaking changes.

[Freyert]

It's not a breaking change. cradle was already taking all the various interfaces for adding authentication to a connection, and transforming it into an object like the one below:

{
  user: "xxxx"
  pass: "yyyy"
}

Which is exactly what request expects. username and password are also valid.