- Notifications
You must be signed in to change notification settings - Fork1k
feat: use wildcard Host entry in config-ssh#16096
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
}, | ||
}, | ||
{ | ||
name:"Section is not moved on re-run", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
This test case (and alsoNo prompt on no changes
below) is a bit tricky to support because it requires writing out a file that will exactly match what we generate. I can rework the test to make this possible if needed, though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Hmm, I think I'm fine losing these for now and I'll make a note to come back to it 😎
Rather than create a separate Host entry for every workspace, configurea wildcard such as `coder.*` which can accomodate all of a user'sworkspaces.
ceab646
to3437757
Compare8f02e63
intocoder:mainUh oh!
There was an error while loading.Please reload this page.
Rather than create a separate
Host
entry for every workspace, configure a wildcard such ascoder.*
which can accomodate all of a user's workspaces.Depends on#16088.