Upload protobuf BSR at https://buf.build/

[AndreasBergmeier6176]

I was searching for buildkits protobuf and could not yet find it at buf.build. Would make hosting buildkitd easier.

[jedevc]

All of the protobuf can be found in *.proto - split out for where it's used.

• ops.proto contains the LLB structure
• gateway.proto defines the GRPC API that the frontend communicates to the buildkit backend over
• control.proto defines the high-level GRPC API that the client (buildctl/buildx/build/etc) communicates to the buildkit backend over
• filesync.proto defines the GRPC API to send files over

Hopefully that helps, this seems like a broader question, so I'll move it over to a discussion to continue the conversation.

To add, there's some other complexity, we use the containerd store GRPC to access stores on the client, etc.

[AndreasBergmeier6176]

Just for further input - I need to e.g. produce additional output by running grpc-gateway plugin. The current directory structure is a bit esoteric and makes this quite hard.

[jedevc]

What's your use case? If it's to wrap the Buildkit API in JSON, then you probably only control.proto?

But of course, that comes with the caveat that none of the build/buildx clients will be able to interact with this JSON API, at least without huge structural changes.

[AndreasBergmeier6176]

What's your use case?

My use cases are:

1. Get an overview of the Protocol Buffers / GRPC interfaces in use.
2. Create a L7 Proxy, which can expose Buildkitd

For 1. BSR would help.
For 2. it is necessary to run multiple (protoc) plugins. I think BSR would also help because I think you can only upload to BSR when you adhere to some best practices. So the hope is that after cleanup, running the plugins becomes possible.
I am currently trying to clean up the protos.

[AndreasBergmeier6176]

So now have a first iteration uploaded to https://buf.build/andreasbergmeier6176/buildkit.