NadimYounes opened a new pull request #11097:
URL: https://github.com/apache/airflow/pull/11097


   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   
   Hello, I am fairly new to contributing to larger repositories so I want to 
apologize in advance if there are any mistakes in my Pull Request. 
   
   I am submitting a change that will allow the 
`airflow.providers.ssh.hooks.ssh` to handle encrypted RSA keys. Currently, when 
the SSHHook attempts to run `get_conn()` on an encrypted RSA key it throws the 
error `paramiko.PasswordRequiredException: Private key file is encrypted`. 
   
   I haven't submitted any tests yet as I just want to make sure that this 
change is valid and adds value to the airflow community.
   
   


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

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to