buf.build - HackMD

![](https://luxcapital-website-media.s3.amazonaws.com/wp-content/uploads/2021/12/09203054/Buf-logo-600x330.png) --- Protobuf management done right <https://buf.build/> ---  ## Current state ---- One API publishing its interface Or not  ---- n consumers with their own toolchain ---- ### Caveats Need protobuf compilation  Needs the same `protoc` version  No standard distribution (aka. no metadata)  --- ## Buf Promises --- ### Great documentation <https://docs.buf.build/> --- ### Buf Schema Registry <https://buf.build/explore> ---- Central repository like PyPI for protobufs --- ### Buf cli ---- Manage the entire lifecycle from a single cli ---- Plugin based Build/generate stubs once for all consumers  Distribute standards pre-compiled packages  ---- ### Bonuses Linter  Formatter  Breaking changes detection  BSR publication with doc generation  ---  ### How ? ---- `buf.yaml` The project descriptor ---- ```yaml= version: v1beta1 name: buf.build/LedgerHQ/bitcoin-keychain build: roots: - . lint: use: - DEFAULT except: - RPC_REQUEST_STANDARD_NAME rpc_allow_google_protobuf_empty_requests: true deps: - buf.build/grpc-ecosystem/grpc-gateway ``` ---- `buf.lock` Dependencies are locked and build are reproducibles  ---- `buf.gen.yaml` The build/generation descriptor(s) ---- ```yaml version: v1 plugins: - remote: buf.build/library/plugins/go:v1.27.1-1 out: pb opt: - module=github.com/ledgerhq/bitcoin-keychain/pb - remote: buf.build/library/plugins/go-grpc:v1.1.0-2 out: pb opt: - module=github.com/ledgerhq/bitcoin-keychain/pb ``` ---- `buf.work.yaml` Make workspaces with multiple linked protobuf projects  ---  ### Next steps ? ---- Proposal PR on `vault-protobufs`  Proposal PR merging `bitcoin-keychain` and `vault-keychain`  ---  ### Questions ?