-
Notifications
You must be signed in to change notification settings - Fork 9
Manage Compute engine credentials in addition of oauth2 #92
Comments
Hi @lucienfregosibodyguard, thanks for reporting this. Do you have a traceback? Also, would you be interested in contributing a fix; might be here: |
Yes here are the traceback
We could use something like this Will try to make a PR |
@ahuang11 I tried to use the code snippet above but it doesn't work |
@ahuang11 do you have time to help on this ? Still stuck on my side :/ |
@lucienfregosibodyguard can you try pulling this branch to test? #98 |
Hi @ahuang11 I looked at the PR but it seems that maybe I miss something but I can't see how it can works 😕 |
There might be multiple credentials: I'm looking at Google auth default. https://google-auth.readthedocs.io/en/master/reference/google.auth.html
|
Yes you're right it has a token attribute indeed ! Few remarks :
And I got the error Then I add Hope that helps |
Oh following this We need |
I did a PR |
This should now be fixed in v0.2.6. Please reopen if that's not the case! |
Hi @ahuang11 sadly it's still doesn't work, got a new error
I guess it's related to the sync definition but don't know how to fix it |
Hi Prefect-dbt team,
Following this tread #56
I tried to authenticate within a kubernetes pod associated to a valid service account.
google.auth.default()
returns a compute engine credentials https://google-auth.readthedocs.io/en/master/reference/google.auth.compute_engine.credentials.htmlThen the code fails because of
'Credentials' object has no attribute 'refresh_token'
From what I understood the code expects a https://google-auth.readthedocs.io/en/stable/reference/google.oauth2.credentials.html
Would be super nice to be able to use the compute_engine credentials
The text was updated successfully, but these errors were encountered: