mod tidy from internal repository via ssh fails

php editor Baicao encountered a problem when modding tidy. He tried to operate from the internal warehouse through ssh but failed. This situation may lead to chaos in the code warehouse, affecting the development process and project stability. Before solving this problem, we need to understand the cause of the failure and possible solutions to ensure the health of the code warehouse. Next, we will explore in detail how to solve this problem.

Question content

I am unable to go mod tidy when using the internal github repository. ssh authentication seems to work alone (see log below), but go mod tidy hits the internal repository and throws

[email protected]: permission denied (publickey).
fatal: could not read from remote repository.
please make sure you have the correct access rights and the repository exists.

From my github operation

steps:
            # checks-out the repository under $github_workspace, so the job can access it
            - uses: actions/checkout@v3

            # set up go
            - name: set up go
              uses: actions/setup-go@v4
              with:
                  go-version: 1.20.2
                  cache: false

            - name: add private key to ssh agent
              env:
                private_key: ${{ secrets.shared_deploy_private_key }}
              run: |
                echo "${{ env.private_key }}" > key.pem
                chmod 600 key.pem
                eval "$(ssh-agent -s)"
                ssh-add key.pem
                ssh-add -l -e sha256
                ssh -t [email protected] 2>&1 || true    ### tests ssh auth

            # install dependencies
            - name: install dependencies
              run: |
                  git config --global url."[email protected]:".insteadof "https://github.com/"
                  go clean -modcache  
                  go env -w goprivate=github.com/my-org/*
                  go env -w gonoproxy=github.com/my-org/*
                  go env
                  go mod tidy

LoginAdd private key

agent pid 1766
identity added: key.pem (_redacted_)
3072 sha256:_redacted_ _redacted_ (rsa)
hi my-org/observability-go! you've successfully authenticated, but github does not provide shell access.

RecordInstalling dependencies

go: downloading github.com/pmezard/go-difflib v1.0.0
go: downloading github.com/mattn/go-isatty v0.0.17
go: downloading golang.org/x/sync v0.1.0
github.com/my-org/clan-service/cmd/clanservice imports
    github.com/my-org/observability-go/logging: github.com/my-org/[email protected]: invalid version: git ls-remote -q origin in /home/runner/go/pkg/mod/cache/vcs/d0c7f50097d6054d27fc7949420737cdb6036d1246584bb05f13c6fe75577be2: exit status 128:
    [email protected]: permission denied (publickey).
    fatal: could not read from remote repository.
    please make sure you have the correct access rights
    and the repository exists.

go env output

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/runner/.cache/go-build"
GOENV="/home/runner/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/runner/go/pkg/mod"
GONOPROXY="github.com/my-org/*"
GONOSUMDB="github.com/my-org/*"
GOOS="linux"
GOPATH="/home/runner/go"
GOPRIVATE="github.com/my-org/*"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/hostedtoolcache/go/1.20.2/x64"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/hostedtoolcache/go/1.20.2/x64/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.20.2"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/runner/work/clan-service/clan-service/go.mod"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build4021260014=/tmp/go-build -gno-record-gcc-switches"

What did I miss? How can I do this?

Workaround

Each step runs in a separate process, so operations that modify the current process-scoped environment will not "survive" to the next step.

For example:
You need to re-run eval "$(ssh-agent -s)" in the "Install Dependencies" step to properly set up the environment to communicate with your ssh agent.

The above is the detailed content of mod tidy from internal repository via ssh fails. For more information, please follow other related articles on the PHP Chinese website!