-
Notifications
You must be signed in to change notification settings - Fork 26
Allow Async Google Operators to accept impersonation_chain
and delegate_to
parameters for authentication
#703
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
Conversation
6580114
to
e54d8c3
Compare
Codecov ReportBase: 98.50% // Head: 98.46% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #703 +/- ##
==========================================
- Coverage 98.50% 98.46% -0.04%
==========================================
Files 87 87
Lines 4746 4753 +7
==========================================
+ Hits 4675 4680 +5
- Misses 71 73 +2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
impersonation_chain
and delegate_to
param
impersonation_chain
and delegate_to
paramimpersonation_chain
and delegate_to
param
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need the integration test DAG to contain examples of using the impersonation_chain
and delegate_to
params
5982e54
to
ab64979
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just interested to know how we are testing this.
ab64979
to
6723b41
Compare
73ee033
to
5ffce3f
Compare
impersonation_chain
and delegate_to
paramimpersonation_chain
and delegate_to
param
da34334
to
316283a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are you changing snowflake provider in this PR? It looks like your PR changes for Snowflake came into this PR - which needs to be corrected
Yes snowflake changes are not related to these PR changes, reverting it back |
5f46287
to
7896998
Compare
@phanikumv can you review now |
astronomer/providers/google/cloud/example_dags/example_bigquery_impersonation_key.py
Outdated
Show resolved
Hide resolved
@rajaths010494 @pankajkoti can you review this PR |
44e8e6c
to
e5cef8e
Compare
896b0c1
to
a0bc1f8
Compare
astronomer/providers/google/cloud/example_dags/example_bigquery_impersonation_key.py
Outdated
Show resolved
Hide resolved
astronomer/providers/google/cloud/example_dags/example_bigquery_impersonation_key.py
Outdated
Show resolved
Hide resolved
astronomer/providers/google/cloud/example_dags/example_bigquery_impersonation_key.py
Outdated
Show resolved
Hide resolved
impersonation_chain
and delegate_to
paramimpersonation_chain
and delegate_to
parameters for authentication
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add example dag for dataproc operator as well as you changed the dataproc operator
Google operators ignore authentication parameters
impersonation_chain
which supports connecting with google cloud API without any authentication key by using impersonation chain authentication. These parameters are supported by their sync version operators, So now made a fix to the async Operators to supportimpersonation_chain
anddelegate_to
other type authentication params.Closes: #651