Re: [I] Allow jinja templating connection ids for all third party operators [airflow]

2024-02-29 Thread via GitHub
kimminw00 commented on issue #35259: URL: https://github.com/apache/airflow/issues/35259#issuecomment-1970621106 I collected all third party operators which have connection IDs. Third party operators which have connection IDs [ ] Airbyte [ ] Alibaba [ ] Amazon

Re: [I] Allow jinja templating connection ids for all third party operators [airflow]

2024-02-19 Thread via GitHub
Taragolis commented on issue #35259: URL: https://github.com/apache/airflow/issues/35259#issuecomment-1953182638 I think it might be a good first issue, I also required to collect all connection ID from the existed operators and list them, so everyone could pick up and make the changes.

Re: [I] Allow jinja templating connection ids for all third party operators [airflow]

2023-10-30 Thread via GitHub
Taragolis commented on issue #35259: URL: https://github.com/apache/airflow/issues/35259#issuecomment-1784993978 This might be blocked by https://github.com/apache/airflow/issues/29069 . In general you could extend `S3CreateObjectOperator.template_fields` by create custom

[I] Allow jinja templating connection ids for all third party operators [airflow]

2023-10-29 Thread via GitHub
kimminw00 opened a new issue, #35259: URL: https://github.com/apache/airflow/issues/35259 ### Description We use staging and prod S3s(Ceph for example) in our office. So there are often cases where DAGs are running with connection ids changed. We prefer to use Param rather than