pydata-google-auth
pydata-google-auth copied to clipboard
ENH: provide config options for changing default client secrets (and scopes)
When pydata-google-auth
is used in contexts where the API is not enabled on the default GCP project that owns the client secrets or the default scopes do not include the desired product / operation, authorization errors are encountered.
It would be difficult to get pydata-google-auth
verified for every combination of scopes, so a better long-term solution would be to encourage people to provide their own client secrets files. Imagine use cases such as notebook hosting services or an enterprise fleet which wants data scientists to use its approved version of pandas.
Hi @tswast , I would like to work on this issue. Can you please assign it to me?