Add overload for private key authentication on sftp configuration builder #1834
Conversation
This file contains 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
|
@dotnet-policy-service agree |
sungam3r
reviewed
Jul 3, 2023
|
@IamMartinPeek Thanks. I'm fine to merge after updating API approval file. |
sungam3r
reviewed
Jul 3, 2023
|
Ah, CI is disabled, see #1018 . OK, I merge this as is. |
Closed
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.
What this PR does / why we need it:
Which issue(s) this PR fixes: related to: it allows private key file authentication for sftp configuration also when keyfile has no password
Please reference the issue this PR will close: #[1833]
Special notes for your reviewer:
Does this PR introduce a user-facing change?: not really it just extends functionallity
Please make sure you've completed the relevant tasks for this PR, out of the following list: