Cloning via ssh isn't working in Lambda

[mmuller88]

Using the ssh url for the cloning step works locally (with running JEST local test) but not in a Lambda.

Steps to reproduce:

• deploy and run the lambda

Error:

{
  "errorType": "Error",
  "errorMessage": "Cloning into 'aws-cdk-staging-pipeline'...\nCould not create directory '/home/sbx_user1051/.ssh'.\r\nFailed to add the host to the list of known hosts (/home/sbx_user1051/.ssh/known_hosts).\r\nPermission denied (publickey).\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n",
  "trace": [
    "Error: Cloning into 'aws-cdk-staging-pipeline'...",
    "Could not create directory '/home/sbx_user1051/.ssh'.\r",
    "Failed to add the host to the list of known hosts (/home/sbx_user1051/.ssh/known_hosts).\r",
    "Permission denied (publickey).\r",
    "fatal: Could not read from remote repository.",
    "",
    "Please make sure you have the correct access rights",
    "and the repository exists.",
    "",
    "    at Object.action (/var/task/index.js:1611:26)",
    "    at PluginStore.exec (/var/task/index.js:1644:27)",
    "    at /var/task/index.js:2044:39",
    "    at new Promise (<anonymous>)",
    "    at GitExecutorChain.handleTaskData (/var/task/index.js:2042:14)",
    "    at GitExecutorChain.<anonymous> (/var/task/index.js:2026:42)",
    "    at Generator.next (<anonymous>)",
    "    at fulfilled (/var/task/index.js:1949:26)",
    "    at processTicksAndRejections (internal/process/task_queues.js:93:5)"
  ]
}

Let me know if you want more explanation how I test it locally. So far you can have a look here: https://github.com/mmuller88/autobrancherdaily/blob/master/test/handlers/brancher.test.ts#L1