forikal-uk
commented
6 years ago The pattern:
If the user provides:
We assume OAuth authentication with google. Not services. This is to ensure that access is granted on a user-by-user basis and not granted on a tool-by-tool basis. Some users should be prevented access to some GSuite data.
Settings Rules Pseudocode:
client-secret-file
findCredentialsPathOption
if none findCredentialsPathConfigSetting
if none, error.
access-token-file
findAccessTokenFileOption
if none findAccessTokenFileConfigSetting
if none, use default AccessTokenFile.
findXConfigSetting
findConfigFilenameOption
if found set configFilename to findConfigFilenameOption else use default configFilename
findConfigFile
if not found
error.
findSetting
if found return value, else return null.
If would also be handy if client-secret-file and access-token-file could be absolute as well as their current relative paths. Absolute paths would allow the user to run a command from anywhere in the tree without having to hack at the new relative path.
As a user of an Xml Authoring Project, I can set one config file with my Google API connection settings, key client file locations, etc, so that one config file in the project can be used for most Commands.
Notes:
Multiple developers create the commands at the same time, so now is the time to refactor to deduplicate implementations and ensure a consistent interface for the user, where possible, across the suite of tools.