v0.5.0 - exporting to Git repo doesn't find/utilize private key file successfully

[fletcherpete72]

Using v0.5.0 - Exporting to Git repo doesn't find/utilize private key file successfully. The only way I've found to get it to work is to run an ssh-agent and add the private key to the agent:

`[peter.fletcher@localhost ipctl-binary]$ ipctl export project "Get Audit History Project" --repository git@gitlab.com:iap-projects/get-gateway-audit-history.git
Error: failed to clone the repository: error creating SSH agent: "Error connecting to SSH_AUTH_SOCK: dial unix /tmp/ssh-UnNBLE1ldbjg/agent.103976: connect: no such file or directory"

[peter.fletcher@localhost ipctl-binary]$ ipctl export project "Get Audit History Project" --repository git@gitlab.com:iap-projects/get-gateway-audit-history.git --private-key-file ~/.ssh/id_rsa
Error: failed to clone the repository: error creating SSH agent: "Error connecting to SSH_AUTH_SOCK: dial unix /tmp/ssh-UnNBLE1ldbjg/agent.103976: connect: no such file or directory"

[peter.fletcher@localhost ipctl-binary]$ eval "$(ssh-agent -s)"
Agent pid 104005
[peter.fletcher@localhost ipctl-binary]$ ssh-add ~/.ssh/id_rsa
Identity added: /home/peter.fletcher/.ssh/id_rsa (peter.fletcher@localhost.localdomain)
[peter.fletcher@localhost ipctl-binary]$ ipctl export project "Get Audit History Project" --repository git@gitlab.com:iap-projects/get-gateway-audit-history.git
Successfully exported project Get Audit History Project
`

[fletcherpete72]

VERBOSE OUTPUT:

`[peter.fletcher@localhost ipctl-binary]$ ipctl export project "Get Audit History Project" --repository git@gitlab.com:iap-projects/get-gateway-audit-history.git --private-key-file ~/.ssh/id_rsa --verbose
2025-03-12T17:26:17Z INF connection timeout is 5 second(s)
2025-03-12T17:26:17Z INF Creating new http client
2025-03-12T17:26:17Z INF POST http://rk-iap-2023-2-2:3000/login
2025-03-12T17:26:19Z INF HTTP response is 200 OK
2025-03-12T17:26:19Z INF GET http://rk-iap-2023-2-2:3000/automation-studio/projects?limit=100
2025-03-12T17:26:19Z DBG Request body is empty
2025-03-12T17:26:19Z INF HTTP response is 200 OK
2025-03-12T17:26:19Z DBG {"message":"Successfully retrieved projects","data":[],"metadata":{"skip":0,"limit":100,"total":8,"nextPageSkip":null,"previousPageSkip":null}}
2025-03-12T17:26:19Z INF Found 8 project(s)
2025-03-12T17:26:19Z INF GET http://rk-iap-2023-2-2:3000/automation-studio/projects/67d09ea976c617ecb37211a3/export
2025-03-12T17:26:19Z DBG Request body is empty
2025-03-12T17:26:19Z INF HTTP response is 200 OK
2025-03-12T17:26:19Z DBG {"message":"Successfully exported project","data":{},"metadata":{}}
2025-03-12T17:26:19Z INF Successfully exported project
2025-03-12T17:26:19Z INF temporary folder is /tmp/tmp1342945638
2025-03-12T17:26:19Z DBG source repository url is git@gitlab.com:iap-projects/get-gateway-audit-history.git
2025-03-12T17:26:19Z DBG source reference is
2025-03-12T17:26:19Z DBG uri schema is ssh
Error: failed to clone the repository: error creating SSH agent: "Error connecting to SSH_AUTH_SOCK: dial unix /tmp/ssh-GDv2OEqkvajs/agent.104004: connect: no such file or directory"

2025-03-12T17:26:19Z FTL error="failed to clone the repository: error creating SSH agent: "Error connecting to SSH_AUTH_SOCK: dial unix /tmp/ssh-GDv2OEqkvajs/agent.104004: connect: no such file or directory""
[peter.fletcher@localhost ipctl-binary]$
~`

[privateip]

So far I have been unsuccessful in replicating this issue. What type of system are you running ipctl on?

[fletcherpete72]

I'm running it here:

(deployer-venv) [peter.fletcher@localhost ipctl-binary]$ hostnamectl
Static hostname: localhost.localdomain
Icon name: computer-vm
Chassis: vm
Machine ID: b721b7b316bb4a74b4cc6366ee411dbf
Boot ID: a9a3d7efccb84a869bb64de6d61bdd61
Virtualization: vmware
Operating System: CentOS Stream 8
CPE OS Name: cpe:/o:centos:centos:8
Kernel: Linux 4.18.0-383.el8.x86_64
Architecture: x86-64

[privateip]

@fletcherpete72 I believe I have found the root cause for this issue and have just pushed a new PR (#90) to address this problem. This will go out as part of the 0.7.0 release. Please test again and reopen this issue if the problem still exists.