EasyP

Using Buf-configured Git dependencies

How the EasyP v1 pilot reads proto roots from Git dependencies that use Buf configuration.

An EasyP v1 project lists Git modules in protobuf.mod. A dependency repository can use Buf configuration; EasyP reads that configuration to find its .proto source roots. The consumer does not need to copy those roots into easyp.gen.yaml.

Dependency fileRoots used by EasyP
buf.work.yaml v1directories
buf.yaml v2modules[].path
buf.yaml v1Repository root
buf.yaml v1beta1build.roots, or repository root if omitted

When a dependency has no EasyP or Buf configuration, EasyP uses its repository root. If it has an older EasyP protobuf.mod or easyp.yaml, EasyP also reads its transitive requirements and declared roots.

When adapting an older easyp.yaml, both deps and generation Git inputs contribute requirements. Exact source/version duplicates are removed; different minimums remain visible to MVS, and malformed deps fail explicitly. A matching native protobuf.mod takes precedence. Only metadata is read; dependency plugins are never executed.

# Consumer protobuf.mod
module github.com/acme/service
roots proto
require github.com/acme/buf-contracts v1.2.0
easyp mod tidy
easyp mod download
easyp generate

mod tidy resolves the Git dependency and records the selected commit and content hash in protobuf.lock. Buf Registry dependency names are not converted into Git URLs automatically; declare a suitable Git source in the consumer manifest. Buf include/exclude filters are not yet supported for Git dependency import roots and produce an error.

After mod tidy, mod vendor can copy the locked Git dependency's .proto files into easyp_vendor using the roots extracted from its Buf configuration. See the package manager guide.