Specifying dependencies in Go

Cloud Functions in Go must provide all of their dependencies via either Go modules with a go.mod file, or a vendor directory. Your function cannot specify dependencies using both Go modules and a vendor directory at the same time.

The Go runtime includes a number of system packages in the execution environment. If your function uses a dependency that requires a system package that is not listed, you can request a package.

Using Go modules

Cloud Functions support Go's experimental Modules functionality, which enables you to specify dependencies in a go.mod file at the root of your project. When you deploy your function, dependencies specified in the go.mod file will be fetched and built automatically.

The behavior of Go modules differs depending on whether you are developing inside or outside of GOPATH. To determine whether you are inside GOPATH:

1. Navigate to your project directory.

2. Find your GOPATH by running the command:

   go env GOPATH
   

   This outputs a line similar to:

   GOPATH=YOUR_GOPATH
   

3. Find your current working directory by running:

   pwd
   

If your working directory begins with YOUR_GOPATH, you are inside GOPATH. In this case, generate your go.mod file by running the following three commands:

export GO111MODULE=on
go mod init
go mod tidy

If your working directory does not begin with YOUR_GOPATH, you are outside GOPATH. In this case, generate your go.mod file by running the commands:

go mod init MODULE
go mod tidy

In the above example, MODULE is the name of your module. For example, your module name might be example.com/myproject. The go command automatically detects the module name when you are inside GOPATH.

After you've created a go.mod file, you can use the go get command to fetch dependencies and automatically add them to your project. For example:

go get DEPENDENCY

In the above example, DEPENDENCY is a dependency that you want to add to your function. For example, the command go get cloud.google.com/go/storage adds the Cloud Storage client library to your function.

Using a vendor directory

Warning: If you have both a go.mod file and a vendor directory at the root of your project, the contents of the vendor directory will be ignored when your function is built in the cloud. To ensure that your vendor directory is used, you must exclude the go.mod file from your project's source code prior to deployment. If you are using the gcloud command-line tool, you can ensure that go.mod is not uploaded by using .gcloudignore.

Cloud Functions also allows you to include your dependencies via a vendor directory. Most of the time, vendor directories are maintained with a dependency manager. You can use any dependency manager you like. For example, you can use Go's Modules functionality to create a vendor directory from your go.mod file.

If you have a go.mod file and a vendor directory, the vendor directory will be ignored when you deploy your function. You can use a .gcloudignore file to avoid uploading your go.mod and go.sum files, in which case the contents of your vendor directory will be respected:

1. Create a .gcloudignore file at the root of your project directory with the following contents:

   go.mod
   go.sum
   
   # Also ignore Git directories. Delete the following two lines if you want to
   # upload them.
   .git
   .gitignore
   

2. Create a vendor directory using the contents of your go.mod file by running the following command:

   go mod vendor
   

Using private dependencies

If your function's dependencies are hosted in a repository that is not publicly accessible, you must use a vendor directory to fetch your dependencies before deploying your function. If you plan to use a go.mod file, see the instructions above to avoid conflicts between the go.mod file and the vendor directory.