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

Adding Before (SSH) Connect Command Option #906

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

alvesoaj
Copy link

@alvesoaj alvesoaj commented Jul 12, 2022

It adds a new feature that allow users set one shell command to run before the ssh connection.

  • add an textfield in SSH tab
  • Process it before ssh connection

image

Motivation:
For some cases are necessary add some credentials before try to access ssh jumphost configuration.

DBeaver also has a more elaborated solution:

image

Note: Sorry for the poor (google translator) translations.

@qishibo
Copy link
Owner

qishibo commented Jul 12, 2022

For some cases are necessary add some credentials before try to access ssh jumphost configuration.

is this necessary everytime? I think this operation(push pubkey to jumphost) needs to be executed for only the first time, after adding it, you can ssh to jumphost directly.
so I think this is a very low frequency operation and we can exec it manually.

@qishibo
Copy link
Owner

qishibo commented Jul 12, 2022

and there're 20k+ lines in diff 😂

@alvesoaj
Copy link
Author

For some cases are necessary add some credentials before try to access ssh jumphost configuration.

is this necessary everytime? I think this operation(push pubkey to jumphost) needs to be executed for only the first time, after adding it, you can ssh to jumphost directly. so I think this is a very low frequency operation and we can exec it manually.

yes, it is necessary every time, and of course, it is my case of use. I know other cases (but using DBeaver).

@alvesoaj
Copy link
Author

and there're 20k+ lines in diff 😂

yes, but 99.9% are code formatting

@qishibo
Copy link
Owner

qishibo commented Jul 14, 2022

You'd better revert the lockFileVersion, because the package-lock.json is also worked with nodejs lower than 14, the v2 may cause some compatibility issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants