google.golang.org/api is not a package, you need to import one of the actual packages inside the folder

Closing per @AlexRouSg's comment. (If you're having trouble importing specific subpackages, please reopen with more detail.)

@AlexRouSg @bcmills what if the repo has not Go source (eg a repo if protobufs).
Why should this be out of scope of vgo? (imo it shouldn't)

@millergarym This issue is not about vgo supporting getting repo's with non go files. This is about importing a non go package and having a non go package in the mod file. That is not something vgo would allow you to do.

Currently when vgo gets a package it gets the entire repo. So you shouldn't need to specifically tell it to get the non go files folders.

This is about importing a non go package and having a non go package in the mod file.

@millergarym at present there is no concept of a "non go package": packages are defined by being just that, collections of Go (and related) code. See go help list for the full breakdown of what the go tool understands as the contents of a package.

So whilst this might be a potential future extension of vgo/go, I don't personally see this as being something that will be supported in the short term.

The workaround as described is to drop a single .go file along with a go.mod file as a container for the non Go files you want to package, or to side-step vgo altogether and manage the dependency yourself/using some other tool.