dstandish commented on PR #23560: URL: https://github.com/apache/airflow/pull/23560#issuecomment-1125343762
@Taragolis we should not care what backends users decide to use. they can specify the class name, and airflow will just import it, so it doesn't matter to airflow whether it's custom or built in. here's what i think is a simple and workable approach. if it’s one class, insert at front; (this is current behavior, hence backward compatible) if list of classes, assume that you’re specifying all backends you want searched and in that order. it's a little trickier is to decide how to supply backend_kwargs. but i think we can just require list of dicts. and what we could do is, check the class list first, and if it is list of string, then enforce that backend kwargs must be list of dict and same number of elements. if it's just a single class name (backcompat) then backend kwargs, if supplied, should be dictionary. wdyt -- 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]
