Skip to content
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

Simplify SSH host - for memorising, constructing from URL, and pasting into SSH clients #11355

Open
loujaybee opened this issue Jul 13, 2022 · 3 comments

Comments

@loujaybee
Copy link
Member

One current advantage of the SSH private key connection is that the URL is more stable than before, where you needed to go back to dashboard and copy/paste the access token (which reset on each workspace start).

New SSH key connection format:

Format: {workspace-id}@{workspace-id}.{ssh-subdomain}.{workspace-generation}.{TLD}
Example: gitpodio-website-25tzkerndba@gitpodio-website-25tzkerndba.ssh.ws-eu54.gitpod.io

The new SSH connection is now more stable, but there are still some aspects which could be refined:

  1. Generation included in the name e.g. .ws-eu54.gitpod.io - For new generations this means the URL changes, and it's also not easy to know what the URL will be without starting a workspace and checking the URL.
  2. Duplication of the workspace-id - If possible, it would be better to remove this duplication, for users who want to "memorise" the SSH pattern and/or construct it themselves intuitively using the workspace ID (use case / example: when breaking apart the connection string to paste into SSH clients with username, host, as separate files)
  3. Inclusion of the ssh subdomain - Having a separate URL for SSH is helpful, but also adds additional friction when constructing the URL For other clients, and/or trying to remember the pattern. However, this aspect is probably the least impacting on friction.
@loujaybee loujaybee changed the title Simplify SSH connection string - easier memorising, construct from URL, and paste into SSH clients Simplify SSH host - for memorising, constructing from URL, and pasting into SSH clients Jul 13, 2022
@akosyakov
Copy link
Member

fyi [email protected] should work already, not sure whether we can do anything about cluster generation cc @iQQBot

@iojcde
Copy link

iojcde commented Aug 19, 2022

Could there be a way to completely exclude the cluster from the workspace URL on the SaaS instance? A URL that only points to a workspace ID would be convenient.

If that doesn't work, to solve the issue of cluster name changes(#10288 (comment)), would there be a way to automatically change the link when the cluster changes too (similar to how the current web dashboard works)?

@stale
Copy link

stale bot commented Nov 23, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Nov 23, 2022
@stale stale bot closed this as completed Dec 3, 2022
@loujaybee loujaybee added meta: never-stale This issue can never become stale aspect: ephemeral and removed meta: stale This issue/PR is stale and will be closed soon labels Dec 20, 2022
@loujaybee loujaybee reopened this Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants