Thanks to visit codestin.com
Credit goes to github.com

Skip to content

feat: improve parity between coder ssh and ssh coder.<workspace> #17056

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bpmct opened this issue Mar 21, 2025 · 1 comment
Open

feat: improve parity between coder ssh and ssh coder.<workspace> #17056

bpmct opened this issue Mar 21, 2025 · 1 comment
Assignees
Labels
cli Area: CLI must-do Issues that must be completed by the end of the Sprint. Or else. Only humans may set this.

Comments

@bpmct
Copy link
Member

bpmct commented Mar 21, 2025

Problem Statement

coder ssh is a separate path from coder config-ssh && ssh <coder.workspace>. There are unpredictable behaviors.

  1. For starters, you cannot use coder ssh to just run "one shot command" and get it in stdout
     # works
     ssh coder.fresh ls
     # does not work 
     coder ssh fresh ls
  2. More importantly, it does not respect what you have set in .ssh/config, for example if you have special options around GPG forwarding, etc. This is the root of the customer issue

Proposal

  • When running coder ssh, first attempt to use ssh and read the hosts, then gracefully fall back to the current behavior.
  • Add a flag to prevent coder ssh from reading .ssh/config
  • Allow coder ssh to also run "one shot" commands.

Related Slack Thread

@bpmct bpmct added the must-do Issues that must be completed by the end of the Sprint. Or else. Only humans may set this. label Mar 21, 2025
@matifali matifali added the cli Area: CLI label Mar 24, 2025
@mafredri
Copy link
Member

mafredri commented May 6, 2025

Found this issue in a search, linking for context a 3 year old issue giving additional weight to this feature (as it keeps resurfacing): #2154

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli Area: CLI must-do Issues that must be completed by the end of the Sprint. Or else. Only humans may set this.
Projects
None yet
Development

No branches or pull requests

4 participants