Skip to content

feat: Separate SSH tunnel configuration from database connections #381

@almas-x

Description

@almas-x

Problem

Currently, SSH tunnel settings are tied to each individual connection. Although all drivers support SSH tunneling, the SSH connection information must be entered repeatedly for every database or service connection.

For example, if I want to connect to multiple services (MySQL, Redis, etcd) on the same remote server, I have to input the same SSH information three times.

This can be tedious and prone to mistakes, especially when managing many connections.

Proposed solution

Allow users to manage SSH tunnel configurations as separate, reusable profiles (similar to tools like DataGrip). I should be able to define an SSH profile once and then select it when creating new connections for different services.

This way, the same SSH configuration can be reused across multiple connections.

Alternatives considered

As a workaround, I currently have to re-enter SSH information for every single connection that requires SSH tunneling.

Other database tools like DataGrip allow SSH profiles to be saved and selected when creating new connections, which is much more convenient.

Related database type

N/A / General

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions