potiuk commented on issue #39437:
URL: https://github.com/apache/airflow/issues/39437#issuecomment-2097788381

   I think @o-nikolas it's not as straightforward. I described it in 
https://github.com/apache/airflow/issues/39103 and the problem is that xmlsec 
python bindings v 1.3.14 expects libxmlsec2 to be installed and used and not 
libxmlsec1. This might or might not be a problem for security at any point in 
time and it should be investigated if the dependency can be upgraded (or as 
@eladkal suggests - turned into an optional dependency and handle lack of 
xmlsec with optional amazon provider dependency + helpful instructions on what 
to do). Especially that - as I understand - it's only needed for maybe one 
integration in Amazon provider.
   
   I am happy to guide anyone who would like to take on that task. 
   
   While yes - you can still build the wheel with installing the packages you 
mentioned, it's a blocker or unnecessary hurdle for people who would like to 
install amazon provider on anything else than Airflow PROD image - so while we 
currently have no problems with releasing airflow (because we limitted xmlsec 
python bindings), it simply makes it more difficult for those who install 
amazon provider on their own. Mostly up to the Amazon team to decide how to 
approach it.
   
   There is no need from Airf
   


-- 
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]

Reply via email to