Unclear documentation for the delegate_to parameter
See original GitHub issueHello,
Most GCP operators accept the delegate_to
parameter. It is not super well documented and it can be confusing to users exactly when they would use this as opposed to another conn id.
A little more documentation on the following page would be helpful. https://airflow.readthedocs.io/en/latest/howto/connection/gcp.html
You can get extra points for adding information about Impersonated credentials . This feature is not supported by Airflow, but it is related (ticket).
Are you wondering how to start contributing to this project? Start by reading our contributor guide
Best regards, Kamil
CC: @jaketf
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:12 (11 by maintainers)
Top Results From Across the Web
Delegates | Unreal Engine Documentation
Data types that reference and execute member functions on C++ Objects.
Read more >c# - How do you provide xml comments/documentation for ...
I want to hover over the delegate or have intellisense popup when I type and tell me the descriptions for the the delegate...
Read more >Spring Data JPA - Reference Documentation
Spring Data repository documentation and your module ... To handle parameters in your query, define method parameters as already seen in the ...
Read more >Groovy Language Documentation
Simple delegation; Delegation strategy; Delegate to parameter ... Using such words as method names is potentially confusing and is often best to avoid, ......
Read more >Action<T> Delegate (System) - Microsoft Learn
The parameter of the method that this delegate encapsulates. Examples. The following example demonstrates the use of the Action<T> delegate to print the ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@olchas I’m in favour of 2nd approach. Regarding the deprecation - first I would check if current implementation works. If it does not then I see no reason for deprecation - let us just remove it.
@jaketf, @amithmathew so it would seem that the approach could be to:
delegate_to
andimpersonation_chain
(new argument used for direct impersonation) inGoogleBaseHook
by raising an exception if both arguments are provideddelegate_to
from most Google operators and hooks, leaving it only in G Suite operators and hooksWDYT? CC: @turbaszek