-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Start DX docs for bigquery: client authorization / configuration. #985
Start DX docs for bigquery: client authorization / configuration. #985
Conversation
----------------------------- | ||
|
||
- Use :class:`Client <gcloud.bigquery.client.Client>` objects to configure | ||
your applications. |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Shouldn't you also update |
I missed the |
if (itemName !== 'Datastore' && | ||
itemName !== 'Storage' && | ||
itemName !== 'Pub/Sub' && | ||
itemName !== 'Big Query') { |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Everything looks fine expect for s/Big Query/BigQuery. Do you have a plan in place for actually introducing the code? I don't want to have the doc committed for too long without any corresponding code. |
I mean to flesh out the "usage" doc first, in order to ask for review from the back-end team (similar to the process for pubsub). @jgeewax would you rather see code commits interleaved? |
…gure Start DX docs for bigquery: client authorization / configuration.
@tseaver : No preference from me... I suspect that the BQ team would look at usage docs first and give feedback, but I don't think it's a showstopper if things are interleaved. |
No description provided.