-
Notifications
You must be signed in to change notification settings - Fork 221
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
Use Application Default Credential if gcp.credential is absent #1531
Use Application Default Credential if gcp.credential is absent #1531
Conversation
Set version to 0.11.0-SNAPSHOT Include treasure-data#1502 to run CI.
…e-snapshot v0_11 fix CI on release of snapshot
…lease-of-v0_10-for-v0_11 [V0_11] Disable snapshot release of v0_10
But just doing that would change current task TTL timeout behavior. So, this commit also takes care of it.
…n-group-tasks Set `started_at` in group tasks as well
to `wait` operator
Add `wait` operator by porting https://github.com/yoyama/digdag-wait-op
Thank you for your contribution. |
@yoyama |
@rhase Thank you for adding test cases. Looks good to me 👍 BTW, could you update the target branch to |
I tried to change target branch by "Edit" button of this PR, but that seems to have caused unexpected effect... |
recreated as #1585 |
What this PR changes
Use Application Default Credential (ADC) if gcp.credential secret is not defined.
Applied to bq, bq_ddl, bq_load, bq_extract and gcs_wait.
Motivation
It's very convenient to use ADC when you run digdag on gce or gke because you don't have to manage service account credentials by your self (Google will manage them for you).
You can also test workflow on your machine with your google account by
gcloud auth application-default login
. You don't need service account and gcp.credential secret.