potiuk commented on PR #32876: URL: https://github.com/apache/airflow/pull/32876#issuecomment-1688013185
> Fortunately, there is workaround for this. We can store connections in places other than airflow db. For example, in environment variables... Or secret backends, or even filesystem secret backend. I wouldn't even call it workaround it's pretty standard approach. Also there is no particular reason to store the API credentials as connection in the DB for such API call. It does not even have to use "Connection" mechanism. You can simply make a regular env variable, mounted as secret in K8S for that. The calls to the API via Airflow Python client are not assuming you are going to use Connection for it. It has never meant to be used with Airflow Connections actually, as the whole idea is to call it from "outside" of Airflow (in this case you will call it from "inside" but this is accidental). So credentials can be passed from any source - Connection seems like unnecessary abstraction to use for it. -- 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]
