How to Authenticate a Private Go Module in Google App Engine Standard with Go 1.11?

Authenticating a Private Go Module on Google App Engine Standard Using Go 1.11

When migrating Go App Engine Standard projects to Go 1.11's modules, developers may encounter authentication issues with private modules. Here's how to address the "403 Forbidden" error that occurs during gcloud app deploy:

Problem

Deploying a project that relies on a private module hosted on Bitbucket fails due to lack of authentication for the private repository.

Solution

Instead of setting up credentials for accessing private repositories directly in Google Cloud Build, consider using Go's module replace functionality. This redirects GAE to use local code instead of the remote version.

Directory Structure

Organize your project files as follows:

myService/
    src/
        service.go
        go.mod
    build/
        gae/
            src/        // simlink to ../../src
            modules/    // git ignored, contains cloned modules.
            app.go
            go.mod
            app.yaml

Method:

1. Use git module replace in the build/gae/go.mod to redirect GAE to use local code:

replace bitbucket.org/me/myService => ./src
replace bitbucket.org/me/myModule => ./modules/utils

2. Create a build script that parses the myService/src/go.mod to identify the correct version of the private module and clone it into the build/gae/modules folder.

Pros

• The private module package remains agnostic of GAE, enabling it to be built for other environments (e.g., docker).
• Simplifies dependency management by relying on Go's module system.

Cons

• Complexities may arise if private modules have dependencies on other private modules.

The above is the detailed content of How to Authenticate a Private Go Module in Google App Engine Standard with Go 1.11?. For more information, please follow other related articles on the PHP Chinese website!