Replies: 2 comments
-
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
Beta Was this translation helpful? Give feedback.
0 replies
-
For those kind of things you should rather use discussions. You should likely use task flow tasks where you instantiate SSHHook and simply use the low level methods of the hook directly - rather than usiing SSH Operator - that would be my advice. Then you do no have to use JINJA and have more control over what and when you pass to the SSH Hook. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What do you see as an issue?
Hey there, This is my first post here so forgive me if this is not the correct place.
I have a unique need of Airflow, I need to integrate SFTP&SSH Operator with a dynamic client, meaning I need that every trigger will also prompt for a user and a password, This means that I can't actually create a permanent Connection in the UI.
I find that using SSHHook is the correct approch.
I created a task that receives the params, and does:
Now I recieve the following error:
socket.gaierror: [Errno -2] Name or service not known
Now when trying to just ssh from the same place that runs this dag, works just fine, also setting up a proper connection with a static user and a ssh_conn_id also works.
Solving the problem
I think the correct way of working with SSHHook should still be implemented.
I tried every docs file but none specify about dynamic connection.
Anything else
No response
Are you willing to submit PR?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions