envs and oauth

Right now, oauth credentials don't really support envs - the concept of envs doesn't play well with outh. Our generic oauth implementation require a unique set of client, credential and provider.

Right now we only allow one oauth "env" per credential - we don't support multiple.

This itself is a problem. When I run my sandbox, it won't have an oauth credential in the env, and you can't add a new env. You have to manually set a new credential, which isn't great

But also I think different providers have different needs?

For gmail tokens, I probably want to use the same account to access different things (a different sheet, a different drive folder). So I need one auth signin/account, and I need some means to switch resource in my workflow (how do I do this? I almost want to add more data, like the sheet id, to the credential - now part of my credential is shared across envs, and part is split)

For Salesforce, I probably want one oauth token form my production salesforce database, and one for my sandbox SF database. Is that two credentials? That feels more like two envs - I have two oauth sign ins associated with one credential.

It's tricky.

No files, tests, or entry points are named. Start by clarifying the intended relationship between environments, OAuth credentials, providers, and resources; the issue is ready only when that behavior and its acceptance criteria are agreed.