ssh: Add support for ServerAliveInterval #1336
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have some tasks running in pyinfra that are particularly long. This is within my expectations, but the problem is that paramiko raises EOFError for all the other hosts that are waiting their turn to run the next step.
After looking a bit I realize paramiko doesn't support
SeverAliveIntervalfrom ssh/config, but has a calltransport.set_keepalivedoing the same thing.This PR adds the parsing for
ServerAliveIntervalfrom ssh/config and sets appropriately the keepalive on the transport.