...

go.resolveDependencies=true   
go.collectDependenciesAtRuntime=false
go.dependencyManager=godep

Glide

Glide dependencies are detected using the generic Go resolver, which is based on the glide.yaml file.

...

go.resolveDependencies=true   
go.dependencyManager=glide
go.glide.ignoreTestPackages=false

Go Modules Resolver

The Go Modules resolver detects only the actively-used dependencies in a full dependencies hierarchy. It is based on the Modules manifest file go.mod and requires the Go binary.

Generic Go Resolver

Using the go.collectDependenciesAtRuntime parameter

...

• The go.collectDependenciesAtRuntime is set to true

• The dependency file is available

• The vendor folder is missing

The Unified Agent will perform the following is performed:

1. For Vndr and Dep, the existing dependency file will be renamed in the following format: <dependency_file>-<YYYY.MM.DD>T<HHmmss>+<UTC offset>.<extension> and the pre-step command will be executed.

2. For Godep, the existing Godeps folder name will be renamed in the following format: Godeps-<YYYY.MM.DD>T<HHmmss>+<UTC offset> and the pre-step command will be executed.

3. For all three noted package managers, the vendor folder containing all the relevant dependencies/files will be created. It will also generate a new dependency file.

...

The go.collectDependenciesAtRuntime parameter is irrelevant for the Glide package manager.

Known Limitations

The Unified Agent generic Go resolver provides support for a hierarchy tree for the following packages: Glide, Gopm, Godep, Dep, Govendor and Vndr.
For Gogradle, the Unified Agent will show both direct and transitive dependencies are displayed in a flat structure.

In order to support the retrieval of a project's full hierarchy tree, one of the following requirements must be met:

• The dependency file and vendor folder are available in the project.

• The go.collectDependenciesAtRuntime parameter is set to true and the relevant dependency manager is installed.