-
Notifications
You must be signed in to change notification settings - Fork 85
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
Unexpected command error when using SSH #1031
Comments
We should catch the error that's thrown in the SSH Handler and wrap it in an ImperativeError. Optionally, we can modify Imperative's error output for uncaught errors - I think the error content is clear enough as is, but we could remove the Marking this as enhancement, since the code is working as expected and does provide accurate error output. |
Thank you for raising this issue. |
Thank you for raising this enhancement request. |
I am seeing similar behavior if I have no default SSH profile defined in a team config (and I have a base profile that goes through the APIML). (in 7.x.x and 8.0.0-next.202402271901) |
Unsure why this linked issue wasn't closed with the merging of #2081 so am closing now |
I am getting the following error that tells me to contact the support:
Steps to reproduce:
My profiles do not contain a user name and password but contain an APIML JWT token.
Base:
SSH:
The text was updated successfully, but these errors were encountered: