You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
coder ssh is a separate path from coder config-ssh && ssh <coder.workspace>. There are unpredictable behaviors.
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
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
Problem Statement
coder ssh
is a separate path fromcoder config-ssh && ssh <coder.workspace>
. There are unpredictable behaviors.coder ssh
to just run "one shot command" and get it in stdout.ssh/config
, for example if you have special options around GPG forwarding, etc. This is the root of the customer issueProposal
coder ssh
, first attempt to usessh
and read the hosts, then gracefully fall back to the current behavior.coder ssh
from reading.ssh/config
coder ssh
to also run "one shot" commands.Related Slack Thread
The text was updated successfully, but these errors were encountered: