writecrow / basecamp_api Goto Github PK

Motivation

It's possible that valid credentials existing in development environments could trigger an access
token refresh, thus invalidating the access token in the live environment.

Options considered

1. Suppress the refresh action in non-live environments to the
   cron job (effectively allowing the API still to work, so long as there is a valid access token.

2. Provide a way for environments to negate the credentials stored in the system (e.g., through
   $settings), so that a refresh attempt would fail (the consequence being that attempts to use
   the API would also fail.