potiuk commented on PR #31885: URL: https://github.com/apache/airflow/pull/31885#issuecomment-1645122015
> @stiak Does this mean I need to wait for composer to upgrade their version of package to 10.4.0 for the apache-airflow-providers-google package? You can likely upgrade it yourself. I believe you can upgrade packages independently in Composer and google provider is the same package as any other (unless of course there is a good reason you need to use the composer's variant of the package there - but that's more of a question to composer team. But.  You always have option of copying the code into your custom operator and using it instead. Airflow is flexible, customizable, fully open-source and "Writing code" is precisely that you are doing when authoring DAGs. Copying the code you can see in this PR and creating and using your own operator while waiting for new provider being released is - I think - even easier than authoring a DAG. You can even add it in a common, .airflowignored package in your DAG folder following https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/modules_management.html#typical-structure-of-packages and then the only change to do is instead of "from airflow.providers.google....." do "from my-package" when importing it in DAG. You can even keep the same class name so that when you get a new provider you can swap import back It's all Python and extending it's capabilities by writing code is first-class citizen. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
