Closed vinokurig closed 3 months ago
Hi @vinokurig. Thanks for your PR.
I'm waiting for a devfile member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/test v8-devworkspace-operator-e2e, v8-che-happy-path
@vinokurig: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
/ok-to-test
Thanks for the PR @vinokurig :) I didn't get a chance to properly look at this today, but I should be able to tomorrow (Wednesday).
@AObuchow Thank you for the review. Looks like we need @dmytro-ndp approval after he verifies the functionality.
@musienko-maxim please review, we need QA approval for that one
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: AObuchow, dkwon17, musienko-maxim, vinokurig
The full list of commands accepted by this bot can be found here.
The pull request process is described here
What does this PR do?
We support project clone from ssh urls, but if the ssh key has a passphrase, the project clone step will fail because the default ssh askpass flow will be invoked, but it does not support any other input then a manual input from keyboard. To override the default flow, a script file is used. The passphrase file must be mounted to
/etc/ssh/
folder. TheSSH_ASKPASS
env variables defines the script file for the ssh flow, see: https://man.openbsd.org/ssh-add#ENVIRONMENT. The currentopen-ssh
version does not support theSSH_ASKPASS_REQUIRE
key, so we need to set theDISPLAY
env variable as the command process does not have an associated terminal.What issues does this PR fix or reference?
https://issues.redhat.com/browse/CRW-6614 Fix https://github.com/devfile/devworkspace-operator/issues/1294
Is it tested? How?
PR Checklist
/test v8-devworkspace-operator-e2e, v8-che-happy-path
to trigger)v8-devworkspace-operator-e2e
: DevWorkspace e2e testv8-che-happy-path
: Happy path for verification integration with Che