-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support BigQuery oauth credentials #233
Comments
👍 we would definitely like to have this |
Downloading service account keys is not very good security practice. The better approach is to use OAUTH as described in this article: https://medium.com/@jryancanty/stop-downloading-google-cloud-service-account-keys-1811d44a97d9 One way to do this is to use GOOGLE_APPLICATION_CREDENTIALS as described in: Another way is for Dataform to expect a short-lived OAuth 2.0 access token, either as input to the CLI or from an environment variable like as done by |
I wholeheartedly agree with @thinhha , access tokens would be an ideal mechanism here. |
This is a very relevant reference: https://cloud.google.com/iam/docs/creating-short-lived-service-account-credentials |
more details on how DBT did this here: dbt-labs/dbt-core#2672 |
Currently BigQuery can only be authorized through a service account, which adds significant overhead to setting up a BQ project.
It should be possible to provide oauth credentials when executing against BigQuery.
During
init-creds
add an option to use OAuth for BigQuery projectsSend the user to the oauth connection page with a callback to localhost:someport
Spin up a small server to handle the oauth callback
Write the oauth credentials to the
.df-credentials.json
fileCreate a Dataform OAuth client ID
Support OAuth credentials in the BigQuery adapter and extend the credentials proto to store this
Implement the new init-creds flow above
The text was updated successfully, but these errors were encountered: