-
-
Notifications
You must be signed in to change notification settings - Fork 146
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
Configuration for using alternative terminal apps for SSM session (iTerm as terminal on MacOS) #62
Comments
We could provide a field for the user to select the path to the terminal executable |
Ok once again Google won: https://apple.stackexchange.com/a/360827
|
Thanks @h-svab for the suggestion. We still need a way to let the user select the preferred executable and verify that it's installed. I think we could use a dialog to let the user select the path to the executable. I'd like to know what @urz9999 and @ericvilla think about this. |
Are there any updates on this? |
This feature was not in the roadmap, but we are adding it to match the System Preferences.
But I still need to look for other Operating Systems (Linux and Windows). Definitely is a feature I want to add soon after this coming release. Any other ideas on how to implement this solution?
As seen here, in the executeService, we are already using osascript to open external terminal windows. I'm an iTerm user too 👍 |
I would also like to see this feature; I prefer the new "Windows Terminal" from Microsoft (https://github.com/microsoft/terminal) but Leapp opens cmd.exe by default. Having this configurable would be convenient! :) |
In Leapp v0.10.0 you can start an AWS SSM session through iTerm2 by selecting it in the options menu! Referenced by #176 |
Thanks to @jgrumboe for the Pull Request #184! |
Is your feature request related to a problem? Please describe.
I usually use iTerm as terminal which is superior to the Terminal app included in MacOS. It would be nice to be able to configure the terminal app that is being used for SSM session.
Describe the solution you'd like
Provide a configuration option which terminal should be used for starting a SSM session.
Describe alternatives you've considered
I don't use this feature at the moment but start the ssm session in the terminal of my choice.
The text was updated successfully, but these errors were encountered: