You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At some point, Amagaki will probably require some sort of Google Sheets (or other Google APIs) access, and I want to propose from the start that ama should request the minimum amount of permissions necessary to do a particular task.
So if a user runs what is similar to grow preprocess -p my-google-sheet for example, then a readonly access token should be requested. But if at some point in the future user runs something like grow translations upload (where translations are stored in a Google Sheet), then ama should then request readwrite access. Ama will need a permissions system to handle this case.
The text was updated successfully, but these errors were encountered:
Getting this working with the following scenarios:
oauth2 key file
autoconfigured environment from gcp project
oauth2 flow for user credentials
Amagaki supports server middleware so planning to experiment implementing this as a server middleware plugin, so other plugins that need access to Google stuff can just fetch the auth from this plugin.
At some point, Amagaki will probably require some sort of Google Sheets (or other Google APIs) access, and I want to propose from the start that ama should request the minimum amount of permissions necessary to do a particular task.
So if a user runs what is similar to
grow preprocess -p my-google-sheet
for example, then a readonly access token should be requested. But if at some point in the future user runs something likegrow translations upload
(where translations are stored in a Google Sheet), then ama should then request readwrite access. Ama will need a permissions system to handle this case.The text was updated successfully, but these errors were encountered: