Closed nickmarx12345678 closed 1 month ago
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
Yes , there is another issue working on, will check and update if this can be added along with that.
Apache Airflow Provider(s)
google
Versions of Apache Airflow Providers
apache-airflow==2.5.3 apache-airflow-providers-cncf-kubernetes==7.10.0 apache-airflow-providers-common-sql==1.8.1 apache-airflow-providers-ftp==3.6.1 apache-airflow-providers-google==10.12.0 apache-airflow-providers-http==4.7.0 apache-airflow-providers-imap==3.4.0 apache-airflow-providers-pagerduty==2.1.2 apache-airflow-providers-slack==8.4.0 apache-airflow-providers-sqlite==3.5.0 google-cloud-pubsub==2.18.4
Apache Airflow version
v2.5.3+composer
Operating System
Google Cloud Composer (unsure)
Deployment
Google Cloud Composer
Deployment details
No response
What happened
When attempting to use the Sensor
PubSubPullSensor
in specifically deferrable mode with a non-default gcp connection, we encounter a lack of permissions despite relevant service account having proper permissions (verified via gcloud command line).With the same arguments and connection, in non-deferrable mode, we observe successful sensor operation (ability to wait, pull, and ack messages).
It appears the underlying trigger does not pass along connection id parameters to the hook
In the non-deferrable pathway, we can see the conn_id and impersonation chain passed to the hook
In our triggerer logs, we see related evidence of use of the default gcp conn id.
How to reproduce
roles/pubsub.admin
to a service account on the project or created topicAnything else
No response
Are you willing to submit PR?
Code of Conduct