Add anthropics/connect-rust plugin v0.3.2 #2334
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| source: | ||
| crates: | ||
| crate_name: connectrpc-codegen |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| * | ||
| !Dockerfile |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| # syntax=docker/dockerfile:1.19 | ||
| FROM rust:1.91.1-alpine3.22 AS builder | ||
| RUN apk add --no-cache musl-dev | ||
| WORKDIR /app | ||
| ENV CARGO_REGISTRIES_CRATES_IO_PROTOCOL=sparse | ||
| # The protoc-gen-connect-rust binary is a [[bin]] target in the | ||
| # connectrpc-codegen crate. cargo install compiles it by crate name. | ||
| RUN --mount=type=cache,target=/usr/local/cargo/registry,sharing=locked --mount=type=cache,target=/root/target \ | ||
| cargo install connectrpc-codegen --version 0.3.2 --locked --root /app | ||
|
|
||
| FROM gcr.io/distroless/static-debian12:latest@sha256:87bce11be0af225e4ca761c40babb06d6d559f5767fbf7dc3c47f0f1a466b92c AS base | ||
|
|
||
| FROM scratch | ||
| COPY --link --from=base / / | ||
| COPY --link --from=builder /app/bin/protoc-gen-connect-rust /protoc-gen-connect-rust | ||
| USER nobody | ||
| ENTRYPOINT ["/protoc-gen-connect-rust"] |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| version: v1 | ||
| name: buf.build/anthropics/connect-rust | ||
| plugin_version: v0.3.2 | ||
| source_url: https://github.com/anthropics/connect-rust | ||
| description: Generates ConnectRPC service traits, typed clients, and monomorphic dispatchers for Rust. Compatible with the Connect, gRPC, and gRPC-Web protocols. Passes the full ConnectRPC conformance suite. | ||
| deps: | ||
| - plugin: buf.build/anthropics/buffa:v0.3.0 | ||
| output_languages: | ||
| - rust | ||
| spdx_license_id: Apache-2.0 | ||
| license_url: https://github.com/anthropics/connect-rust/blob/v0.3.2/LICENSE | ||
| registry: | ||
| cargo: | ||
| rust_version: "1.88" | ||
| deps: | ||
| # ConnectRPC runtime: Router, Context, ConnectError, client transports. | ||
| # https://github.com/anthropics/connect-rust/blob/v0.3.2/connectrpc/Cargo.toml | ||
| - name: "connectrpc" | ||
| req: "0.3.2" | ||
| default_features: true | ||
| # Generated service stubs use buffa::Message, buffa::view::OwnedView, | ||
| # buffa::bytes::Bytes directly. Message types live in the buffa SDK | ||
| # crate (via the plugin dep above); this dep is for the runtime API. | ||
| - name: "buffa" | ||
| req: "0.3.0" | ||
| default_features: true | ||
| # Streaming method signatures use futures::Stream. | ||
| - name: "futures" | ||
| req: "0.3" | ||
| default_features: true | ||
| # Client transport bounds reference http_body::Body. | ||
| - name: "http-body" | ||
| req: "1" | ||
| default_features: true | ||
| # The plugin accepts `extern_path=.=<rust_path>` (or the shorthand | ||
| # `buffa_module=<rust_path>`) to tell it where the buffa-generated message | ||
| # types live. BSR should inject this based on the buffa dep's SDK crate | ||
| # name, same as tonic receives extern_path for its prost dep. Leaving | ||
| # opts empty here; please advise if an explicit entry is needed. | ||
| opts: [] | ||
|
Comment on lines
+35
to
+40
Member
There was a problem hiding this comment. should be fine to leave this empty, and the BSR will figure out |
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
silly non-expert-in-rust question: I see the default features; those don't include the
tlsfeature, but is that just something that is "enabled" by having the various "deps" in the sub-features installed? (Mostly trying to confirm that someone consuming this generated SDK could still use the TLS features.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[claude code] Yes — Cargo features are additive and unified per-crate across the dependency graph. The generated SDK crate only needs
connectrpc's default features for the generated code to compile, so that's all it declares. A consumer who wants TLS adds their own direct dependency in their application'sCargo.toml:Cargo then compiles
connectrpconce with the union of features requested by both the SDK crate and the application, sotls(andclient-tls/server-tls/ any other optional feature) is fully available. Same model the tonic SDK crates use — the SDK doesn't gate runtime features.