Split out get_or_create

[stacksjb]

Currently, any function that calls config calls get_or_create which automatically creates the config.

These should be mostly updated to use a get and return an error; if no config exists we should get a consistent error and prompt user to run tod auth login (or similar setup commands) that can use get_or_create instead of auto creating the config.

get_or_create can then re-use each of those individual functions

However this may require some serious review and digging.

[alanvardy]

I like this, it will make the code a lot more predictable.

[stacksjb]

Pseudo code what it will do:
Get -> returns current configuration, otherwise fails
Create -> returns newly created config struct

Get_or_create -> called Boolean check, if exists calls get, otherwise calls create

Are there specific functions besides auth login and config open that that should call get_or_create?

[alanvardy]

I think that config open should just call get. auth login is probably the only thing that should call get_or_create and everything else can just return an error telling the user to auth login if there is no config or token.