bufdev

Here's how we maintain multiple sets: https://github.com/bufbuild/buf/tree/main/data/template You can use the `--template` flag https://github.com/bufbuild/buf/blob/main/make/buf/all.mk#L104

I think for now we're going to close this: the canonical way to do this currently is with having multiple `buf.gen.yaml` files, and we don't want to mix responsibilities between...

We're going to reconsider this

I don't think we want to special-case `protoc-gen-validate` annotations: - It's a rabbit hole - do we also special-case `google.api`? `gogoproto`? The newest library that comes out? - `protoc-gen-validate` looks...

For future reference, this is roughly what we want: ```diff diff --git a/data/template/buf.go-client.gen.yaml b/data/template/buf.go-client.gen.yaml index 68b84740..7b522a82 100644 --- a/data/template/buf.go-client.gen.yaml +++ b/data/template/buf.go-client.gen.yaml @@ -5,6 +5,12 @@ managed: enabled: true go_package_prefix: default:...

I don't believe this path will necessarily be relative to a user's working directory - this could be within a tarball, git repo, etc.

What is your workflow without these being published?

Yep, but what is your workflow without these being published? ie what would be the major value add here?

Just a general note: I started this work a while back: https://github.com/bufbuild/buf/blob/main/private/pkg/spdx/cmd/spdx-go-data/main.go https://github.com/bufbuild/buf/blob/main/private/gen/data/dataspdx/dataspdx.gen.go This was meant to match what NPM does basically.

This would be pretty trivial if we added `UserService.GetUsers` and `OrganizationService.GetOrganizations`, that's all we really need to do.