actions/setup-ssh: Direct access to runner machines over Tailscale#34
Conversation
Useful for debugging issues with GitHub Actions workflows, particularly in cases when similar commands work on your machine but not the runner machines.
|
Note that I haven't (yet) defined a [Update: See also the notes about this I dropped in Slack.] |
|
To personally test this, you'll need:
Steps:
|
This mode means devices will always be ephemeral, even if the auth key isn't. That's what we want here for runner machines. It also deregisters devices immediately upon exit, without having to separately perform an explicit `tailscale logout` or wait the normal period before automatic removal.
…using our setup-ssh action in the nextstrain/.github repo. Useful to test changes to setup-ssh, but also useful to have available for debugging runners outside of the context of any specific workflow (i.e. in which you could use setup-ssh directly). Provided as a workflow template, not an actual runnable workflow in this repository, because this workflow should only be used in private repositories (which this repo is not). Instead, see our nextstrain/private repo for a runnable copy of this workflow.¹ ¹ https://github.com/nextstrain/private/actions/workflows/debugging-runner.yaml
|
I was using this again on Friday to try out commands on a runner while adding the Singularity runtime to Nextstrain CLI's CI. Since it's working well for me and there's zero consequence right now if it doesn't, I'm going to merge this. That will let me address https://github.com/nextstrain/private/pull/72#discussion_r1052611618. We can address providing an org-level Tailscale auth key (per #34 (comment)) separately. |
victorlin
left a comment
There was a problem hiding this comment.
Thanks for setting this up! Works for me. Made a few changes over at https://github.com/nextstrain/private/compare/93cfadce8e28580c868576d6e3d980b9c99c09fe...4a5756f450d0a56e26ea4cde6981d4bd3df9a83b based on my experience.
Useful for debugging issues with GitHub Actions workflows, particularly in cases when similar commands work on your machine but not the runner machines.
See also the README.
Related issue(s)
Testing