@@ -30,9 +30,7 @@ OAuth flow for installed applications.
3030| name | type | required? | default | description |
3131| :-------------------------------------| :------------| :-----------| :-------------------------| :-----------------------|
3232| mode | string | optional | "append" | See [ Mode] ( #mode ) |
33- | auth_method | string | optional | "private_key" | ` private_key ` , ` json_key ` or ` compute_engine `
34- | service_account_email | string | required when auth_method is private_key | | Your Google service account email
35- | p12_keyfile | string | required when auth_method is private_key | | Fullpath of private key in P12(PKCS12) format |
33+ | auth_method | string | optional | "json\_ key" | ` json_key ` , ` compute_engine ` , or ` application_default `
3634| json_keyfile | string | required when auth_method is json_key | | Fullpath of json key |
3735| project | string | required if json_keyfile is not given | | project_id |
3836| dataset | string | required | | dataset |
@@ -108,9 +106,8 @@ Following options are same as [bq command-line tools](https://cloud.google.com/b
108106out :
109107 type : bigquery
110108 mode : append
111- auth_method : private_key # default
112- service_account_email : ABCXYZ123ABCXYZ123.gserviceaccount.com
113- p12_keyfile : /path/to/p12_keyfile.p12
109+ auth_method : json_key # default
110+ json_keyfile : /path/to/json_keyfile.json
114111 project : your-project-000
115112 dataset : your_dataset_name
116113 table : your_table_name
@@ -167,22 +164,9 @@ NOTE: BigQuery does not support replacing (actually, copying into) a non-partiti
167164
168165There are three methods supported to fetch access token for the service account.
169166
170- 1. Public-Private key pair of GCP(Google Cloud Platform)'s service account
171- 2. JSON key of GCP(Google Cloud Platform)'s service account
172- 3. Pre-defined access token (Google Compute Engine only)
173-
174- # ### Public-Private key pair of GCP's service account
175-
176- You first need to create a service account (client ID),
177- download its private key and deploy the key with embulk.
178-
179- ` ` ` yaml
180- out:
181- type: bigquery
182- auth_method: private_key # default
183- service_account_email: ABCXYZ123ABCXYZ123.gserviceaccount.com
184- p12_keyfile: /path/to/p12_keyfile.p12
185- ` ` `
167+ 1. JSON key of GCP(Google Cloud Platform)'s service account
168+ 1. Pre-defined access token (Google Compute Engine only)
169+ 1. [Application Default](https://cloud.google.com/docs/authentication/production)
186170
187171# ### JSON key of GCP's service account
188172
211195 }
212196` ` `
213197
214- # ### Pre-defined access token(GCE only)
198+ # ### Pre-defined access token (GCE only)
215199
216200On the other hand, you don't need to explicitly create a service account for embulk when you
217201run embulk in Google Compute Engine. In this third authentication method, you need to
@@ -224,6 +208,16 @@ out:
224208 auth_method: compute_engine
225209` ` `
226210
211+ # ### Application Default
212+
213+ See https://cloud.google.com/docs/authentication/production
214+
215+ ` ` ` yaml
216+ out:
217+ type: bigquery
218+ auth_method: application_default
219+ ` ` `
220+
227221# ## Table id formatting
228222
229223` table` and option accept [Time#strftime](http://ruby-doc.org/core-1.9.3/Time.html#method-i-strftime)
0 commit comments