Target dir for input:git_repo

[hollyhox-21]

Feature

Please add the target directory where the compiled proto file will be placed

  - git_repo: "https://github.com/some-repo.git"
    branch: master
    subdir: endpoints
    target: pkg/some_dir/some_grpc_services

[bufdev]

We do not understand what you are asking for - output locations are specified in the plugins configuration, not the inputs. Can you clarify?

[hollyhox-21]

I mean override out for input git_repo. I want to compile outside proto files. And use their for create client.
For example: There is service A(go) and service B(java). Both are gRPCs. Service B is a client of service A. I want to generate .pb files through my plugins.

I want to see that view:

**buf.gen.yaml:**
version: v2
plugins:
  - remote: buf.build/protocolbuffers
    out: pkg/api
    opt:
      - paths=source_relative
inputs:
  - directory: api
  - git_repo: "https://github.com/serviceA.git"
     branch: master
     subdir: api
     out: pkg/remote_api
     
     
.
├── api
│ └── serviceB
│     └── foo.proto
├── pkg
│ ├── api
│ │ └── serviceB
│ │     ├── foo.pb.java
│ │     ├── foo.pb.gw.java
│ │     ├── foo.swagger.json
│ │     └── foo_grpc.pb.java
│ └── remote_api
│         └── api
│                 └── serviceA
│                         ├── bar.pb.java
│                         ├── bar.pb.gw.java
│                         ├── bar.swagger.json
│                         └── bar_grpc.pb.java
└── tree.txt

[bufdev]

I still don't understand. Can you create an example repository with what you want to see, and the output?

[doriable]

The inputs key in buf.gen.yaml currently does not interact with the plugins key -- the destination of your output is configured in plugins on a per-plugin basis, and then each plugin is applied to each input.

If you want a different plugin configuration, our current guidance is to define a second file, e.g. buf.remote.gen.yaml, and have your the remote repository you are targeting and plugin configurations, e.g.

**buf.gen.yaml:**

version: v2
plugins:
  - remote: buf.build/protocolbuffers
    out: pkg/api
    opt:
      - paths=source_relative
inputs:
  - directory: api

**buf.remote.gen.yaml:**
version: v2
plugins:
  - remote: buf.build/protocolbuffers
    out: pkg/remote_api
    opt:
      - paths=source_relative
  - git_repo: "https://github.com/serviceA.git"
     branch: master
     subdir: api

And then you can use the second file with buf generate --template buf.remote.gen.yaml.

We have similar requests in the past, #3060, I can close this as a duplicate and we can combine the discussions. Thanks!