invalid value "nas1" for --exit-node; must be IP or unique node name

Open
#123 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, typescript
Domain
ci-cd, networking

Research direction

Start with the tailscale/github-action@v2 entry point and compare how its args value invokes --exit-node with the two Tailscale CLI commands shown in the issue. Reproduce the workflow using nas1, then determine what change is needed for the action to accept the same unique node name successfully.

Written by the indexing model from the issue text.

Description

I am trying to use tailscale/github-action@v2 Github action. You can find my Github action code below

name: tailscale test

on:
  workflow_dispatch:

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v2

      - name: Tailscale
        uses: tailscale/github-action@v2
        with:
          authkey: ${{ secrets.TAILSCALE_AUTHKEY }}
          args: --reset --accept-routes --exit-node nas1
          hostname: github-action-${{ github.run_id }}

However, when running above action, I am getting error invalid value "nas1" for --exit-node; must be IP or unique node name

image

I can successfully run Tailscale using nas1 as exit node when using Tailscale CLI

sudo tailscale up --authkey "${{ secrets.TAILSCALE_AUTHKEY }}" --hostname "github-action-${{ github.run_id }}"
sudo tailscale up --reset --accept-routes --exit-node "nas1" --hostname "github-action-${{ github.run_id }}"

Could you guide me on how to debug this issue, please?

Dominant language
TypeScript
Stars
938
Forks
137
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tailscale/github-action

All issues in tailscale/github-action

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.