[Bug]: SSH connection command no longer printed after workspace setup

[YassineElbouchaibi]

Before submitting

• I have searched existing issues to confirm this is not a duplicate
• I am running the latest version of DevPod

What happened?

After running devpod up, the SSH command needed to connect to the workspace is no longer printed to the user. Instead, a generic SSH configuration completed in workspace message is shown.

This was introduced in commit c8f60ee, which replaced:

log.WithFields(logrus.Fields{"workspace": client.Workspace()}).Info("SSH command available: ssh " + client.Workspace() + ".devpod")

with:

log.Info("SSH configuration completed in workspace")

in cmd/up.go.

What did you expect to happen instead?

After devpod up completes, the CLI should print the exact SSH command the user can run to connect to the workspace, e.g.:

Run 'ssh my-workspace.devpod' to ssh into the devcontainer

Steps to reproduce

1. Run devpod up <workspace>
2. Observe the output — no SSH command is printed
3. Compare with upstream loft-sh/devpod which still prints the command

devcontainer.json

N/A

Error output / logs

N/A

How often does this happen?

Every time

Operating system

N/A

Linux distribution (if applicable)

N/A

Architecture

N/A

Desktop app or CLI?

CLI only

DevPod version

N/A

DevPod provider

N/A

Provider version

N/A

Screenshots

N/A

Anything else?

Regression relative to earlier fork state (and loft-sh/devpod upstream, which still emits an equivalent message). The fix is a one-line change in cmd/up.go — restore a message that includes the workspace name so the user knows exactly which SSH command to run, e.g. log.WithFields(logrus.Fields{"workspace": client.Workspace()}).Info("SSH command available: ssh " + client.Workspace() + ".devpod").

[skevetter]

The upstream project emits logs to console throughout. It is a fairly big change to move away from that, but my position is that the log messages to stdout should be cleaned up. Information about the workspace should be obtained through using get or describe commands. To this end, I do not see the change as a bug but I am open to someone making a case to keep this in output.

[YassineElbouchaibi]

For added context, I do not use the GUI. I use the CLI, and when sharing this tool with others, I felt it would be more intuitive to print the ssh command right after the up command. That way, people are not left wondering, “What do I do now?” after running up.

Showing the ssh command makes the next step explicit: you can now SSH in and start developing.

EDIT: I agree that this is not a bug! This perhaps a feature request disguised as a bug report 😆