How to buf push this library?

[harrytran998]

I had some custom config with this plugin - yeah, fork this one! But currently, don't know how to buf push this plugin.

I updated + built the code, and generated the new integrations.

Created a buf.yaml file in the root project

version: v2
modules:
  - path: .
    excludes:
      - node_modules
      - protos
    name: buf.build/investtal/ts-proto

But when run buf push --> Display the error bellow. Does anyone have any idea? Hope @stephenh can help me answer this one 🙏 Thanks

...
integration/use-optionals-no-undefined/test.proto:27:17:symbol "optionalstest.OptionalsTest.opt_truth" already defined at integration/use-optionals-deprecated-only/test.proto:23:17
integration/use-optionals-no-undefined/test.proto:28:19:symbol "optionalstest.OptionalsTest._opt_description" already defined at integration/use-optionals-deprecated-only/test.proto:24:19
integration/use-optionals-no-undefined/test.proto:28:19:symbol "optionalstest.OptionalsTest.opt_description" already defined at integration/use-optionals-deprecated-only/test.proto:24:19
integration/use-optionals-no-undefined/test.proto:29:18:symbol "optionalstest.OptionalsTest._opt_data" already defined at integration/use-optionals-deprecated-only/test.proto:25:18
integration/use-optionals-no-undefined/test.proto:29:18:symbol "optionalstest.OptionalsTest.opt_data" already defined at integration/use-optionals-deprecated-only/test.proto:25:18
integration/use-optionals-no-undefined/test.proto:31:7:symbol "optionalstest.OptionalsTest.TranslationsEntry.key" already defined at integration/use-optionals-deprecated-only/test.proto:27:7
integration/use-optionals-no-undefined/test.proto:31:15:symbol "optionalstest.OptionalsTest.TranslationsEntry.value" already defined at integration/use-optionals-deprecated-only/test.proto:27:15
integration/use-optionals-no-undefined/test.proto:31:23:symbol "optionalstest.OptionalsTest.TranslationsEntry" already defined at integration/use-optionals-deprecated-only/test.proto:27:23
integration/use-optionals-no-undefined/test.proto:31:23:symbol "optionalstest.OptionalsTest.translations" already defined at integration/use-optionals-deprecated-only/test.proto:27:23
integration/use-optionals-no-undefined/test.proto:36:6:symbol "optionalstest.StateEnum" already defined at integration/use-optionals-deprecated-only/test.proto:30:6
integration/use-optionals-no-undefined/test.proto:37:3:symbol "optionalstest.UNKNOWN" already defined at integration/use-optionals-deprecated-only/test.proto:32:3; protobuf uses C++ scoping rules for enum values, so they exist in the scope enclosing the enum
integration/use-optionals-no-undefined/test.proto:38:3:symbol "optionalstest.ON" already defined at integration/use-optionals-deprecated-only/test.proto:33:3; protobuf uses C++ scoping rules for enum values, so they exist in the scope enclosing the enum
integration/use-optionals-no-undefined/test.proto:39:3:symbol "optionalstest.OFF" already defined at integration/use-optionals-deprecated-only/test.proto:34:3; protobuf uses C++ scoping rules for enum values, so they exist in the scope enclosing the enum

[stephenh]

Hi @harrytran998 ! Custom config/forking is exactly the sort of thing ts-proto is meant to be used for. :-)

In terms of buf push, no, I really don't know much about the buf platform -- at one point, ts-proto's CI pipeline could push up our own latest builds, but then buf switched to only doing internally-controlled publishing of community plugins like ours, so ngl I didn't know you could still buf push -- although I guess if you're using their repos as a client, that makes a lot of sense.

But otherwise I'd have to defer to @timostamm ; sorry Timo is I'm cc-ing you on some should-have-been-obvious issue. Thanks!

[harrytran998]

Thanks for the quick answer @stephenh. Because I see the ts-proto[https://buf.build/community/stephenh-ts-proto?version=v2.6.1] is a plugin in the buf plugins system. We used it and were happy with that. Currently, we need to customize some of the configs and push that into buf plugins.

So this will be better if we have a document to guide "How to customize ts-proto and publish that into another platform like buff"

[timostamm]

Hey Harry, buf push pushes Protobuf files to the schema registry. Anyone could push custom plugins to the BSR in the past, but the policy has changed for security reasons. Only private schema registry instances accept custom plugin pushes now, which is a paid feature, unfortunately.

The plugins available on the public BSR are maintained by Buf, in this repository: https://github.com/bufbuild/plugins. You can request for a plugin to be added, but widely adopted plugins are more likely to be accepted.

That said, you definitely don't have to go through the BSR if you don't need BSR features. Here is an example for generating with a local, modified copy of ts-proto:

version: v2
inputs:
  # Just as an example, could also be `- directory: ./proto`
  - module: buf.build/connectrpc/eliza
plugins:
  - local: ["tsx", "./ts-proto/src/plugin.ts"]
    out: src/gen

npx buf generate will run plugin.ts with tsx. Alternatively, you could publish your forked plugin on npmjs.com and depend on the package in multiple other projects.

[harrytran998]

Thank you, appreciate your guys' answers 🚀 It works like a charm!