feat: add winrm connect timeout and retry params#334
Open
Pandapip1 wants to merge 1 commit into
Open
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
1 participant
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.
Submitted on behalf of a third-party: Realtime Robotics
Description
WinRM (at least on tiny11) seems to have an internal 70-second timeout when it hasn't started yet that limits the rate at which WinRM connections are retried. This adds a timeout so that it can fail and retry early, to more quickly respond to when WinRM does become available.
Untested, but does compile and seems trivial enough.
Resolved Issues
N.A.
Rollback Plan
N.A.
Changes to Security Controls
N.A.