[v16] Support AddKeysToAgent in Connect
#47324
Merged
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
github-actions
bot
added
backport
documentation
size/sm
tsh
|
🤖 Vercel preview here: https://docs-16kf38uve-goteleport.vercel.app/docs/ver/preview |
gzdunek
approved these changes
Oct 8, 2024
avatus
approved these changes
Oct 8, 2024
Merged
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.
Backport #47270.
The only conflict was in the docs actually, as
ssh.forwardAgentistrueby default on v16 butfalseon master.changelog: Added a config option to Teleport Connect to control how it interacts with the local SSH agent (
sshAgent.addKeysToAgent)