Skip to content

feat: add short_description to dataplane v1 FieldSpec - #2600

Open
prakhargarg105 wants to merge 1 commit into
redpanda-data:masterfrom
prakhargarg105:short-description-field
Open

feat: add short_description to dataplane v1 FieldSpec#2600
prakhargarg105 wants to merge 1 commit into
redpanda-data:masterfrom
prakhargarg105:short-description-field

Conversation

@prakhargarg105

Copy link
Copy Markdown

What

Adds an optional string short_description = 14; to message FieldSpec in proto/redpanda/api/dataplane/v1/pipeline.proto, plus the regenerated Go / TypeScript / OpenAPI code (task proto:generate).

Why

Redpanda Connect ≥ v4.104.0 emits a short_description for config fields (redpanda-data/connect#4638, benthos redpanda-data/benthos#463): a plain-text, ≤140-char summary suitable for inline help in the pipeline config editor, unlike description which is Asciidoc documentation prose often hundreds of characters long (e.g. postgres_cdc heartbeat_interval is 715 chars).

This proto field is the transport hop that lets the value reach the Console UI. Follow-ups (separate PRs): the connect-api mapping in cloudv2 to populate it, and frontend rendering.

Compatibility

Adding a new proto3 field is wire- and JSON-compatible in both directions: servers that don't populate it send nothing (clients see ""), and older clients ignore the unknown field. FieldSpec is component-schema metadata for the config editor only — running pipelines never consume it — so no coordination with deployed Connect versions is required.

Testing

  • buf lint / buf format pass (run as part of task proto:generate).
  • Verified the generated Go diff is exactly the new field + getter + descriptor bytes; go build ./pkg/protogen/... passes.
  • v1alpha2/v1alpha3 OpenAPI outputs unchanged (FieldSpec is v1-only).

🤖 Generated with Claude Code

Adds an optional short_description field to the pipeline component
schema FieldSpec, carrying the plain-text inline help introduced in
Redpanda Connect 4.104.0 (redpanda-data/connect#4638). The field is
empty until the connect-api populates it; adding field 14 is wire- and
JSON-compatible in both directions, so no coordination with deployed
pipelines or older UI builds is required.

Generated code (Go, TypeScript, OpenAPI) regenerated via task
proto:generate.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant