Google Operators don't support all authentication parameters

[m1racoli]

Describe the bug

The following implementation of Google operators ignore authentication parameters delegate_to and impersonation_chain. These parameters are supported by their sync counterparts as it is documented (where applicable).

• BigQueryInsertJobOperatorAsync
• BigQueryGetDataOperatorAsync
• BigQueryIntervalCheckOperatorAsync
• DataprocCreateClusterOperatorAsync
• DataprocDeleteClusterOperatorAsync
• DataprocSubmitJobOperatorAsync
• DataprocUpdateClusterOperatorAsync

It is important that those parameters are respected when loading the hook during the synchronous execute call as well as in the corresponding defer call to the trigger (and thus in the trigger as well).

To Reproduce

Using impersonation_chain with BigQueryInsertJobOperatorAsync will result in the task using the identity provided by the credentials of the GCP connection.

Expected behaviour

It should use the identity as defined in impersonation_chain.

[phanikumv]

Thank you @m1racoli for creating the issue!

[m1racoli]

Thanks! I am not sure I managed to discover all cases. My findings are based on the search for :param impersonation_chain: in the doc string. The BigQuery and GCS sensors as well as the GKEStartPodOperatorAsync seem to support these parameters already.