Skip to content

feat: add protoc-gen-connect-openapi to codegen pipeline #88

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
haasonsaas merged 2 commits into from
Apr 16, 2026
Merged

feat: add protoc-gen-connect-openapi to codegen pipeline #88

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1fedf36
feat: add protoc-gen-connect-openapi to codegen pipeline
haasonsaas Apr 16, 2026
3ed6af8
chore: commit generated OpenAPI specs from protoc-gen-connect-openapi
haasonsaas Apr 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions buf.gen.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,3 +17,9 @@ plugins:
# Python
- remote: buf.build/protocolbuffers/python
out: gen/python
# OpenAPI — generates Connect-compatible OpenAPI v3.1 specs per service.
# Consumed by mcp-openapi to produce MCP tool definitions for agent-mcp.
- remote: buf.build/community/sudorandom-connect-openapi:v0.19.1
out: gen/openapi
opt:
- path=
Copy link
Copy Markdown

@cursor cursor bot Apr 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Empty path= option likely causes generation failure

High Severity

The opt for the OpenAPI plugin sets path= to an empty string. The path option in protoc-gen-connect-openapi specifies a single output filename (e.g., path=openapi.yaml). An empty value will either cause the plugin to attempt writing to an empty-named file (failing generation) or be a silent no-op, making the entire opt: block unnecessary dead configuration. If the intent was per-file output, the opt: section can be removed entirely. If a single merged file was intended, a filename is needed.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 1fedf36. Configure here.

Copy link
Copy Markdown

@cursor cursor bot Apr 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bugbot Autofix determined this is a false positive.

The pinned protoc-gen-connect-openapi version treats path= as an empty Path, so buf generate succeeds and falls back to per-proto-file output.

You can send follow-ups to the cloud agent here.

Loading
Loading