Add ability to execute ssh command#149
Conversation
|
Currently the command doesn't work for me, so I'd like to get to the bottom of that before removing this from draft. |
|
The |
dff745d to
ba8baf8
Compare
|
Thanks for the explanation; I had wondered why the command was hidden! I'm more than a little hazy on this, but it looks like the identity and certificate parameters aren't being propagated to the jump host, causing the connection to be rejected. Switching out Tested on Linux/OpenSSH_8.9p1 and macOS/OpenSSH_9.9p2. |
|
Thanks for re-running the CI on this. I'm a bit confused as to why it's failing just for aarch64; I'll look into it and see if I can figure it out. |
I don't think it's anything to do with what you've done. It's failing to install a dependency on just one architecture. I think I've seen it before with that dependency and I might have fixed it with an update of the version. |
|
Thanks for the pointers @milliams and for re-running the CI again. I'm switching it to draft while I figure out how to reproduce this myself. |
903eec4 to
3597679
Compare
Adds the ability to spawn the ssh command generated using the ssh-command command.
3597679 to
e9afbdc
Compare
|
I'm afraid I'm confused by this. When I run ostensibly the same workflow on my fork of the repository it goes through okay: https://github.com/llewelld/clifton/actions/runs/19760556074 The only difference is that I gave it an annotated tag to avoid an error parsing the version returned by |
|
That's dragging up a memory about the GitHub Actions package cache being the problem. I'll see if I can clear it and if it makes a difference. |
|
Hooray! 🙌 Thank you. I'll drop it out of draft and appreciate your thoughts on whether this is a viable approach. |
Adds the ability to spawn the ssh command generated using the ssh-command command.
Contributes to #48.