chore: replace benthos with redpanda/connect#463
Conversation
WalkthroughThe PR changes Benthos image resolution to Docker Hub’s Redpanda Connect image, updates the deployment image tag to ChangesBenthos Image Update
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (3 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
internal/resources/registries/image.go (1)
14-14: ⚡ Quick winUpdate documentation to reflect the actual registry pattern.
The documentation comment still references
jeffail/, but the actualGetBenthosImageimplementation now usesdocker.redpanda.com/redpandadata/connect. Consider updating this line to reflect the new pattern or removing the outdated reference.📝 Suggested documentation fix
-// public.ecr.aws/<organization>/jeffail/ +// docker.redpanda.com/<organization>/<repository>:<version>🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@internal/resources/registries/image.go` at line 14, The file-level doc comment is out of date: replace or remove the stale registry reference "// public.ecr.aws/<organization>/jeffail/" so it matches the actual image registry used by GetBenthosImage (docker.redpanda.com/redpandadata/connect) — update the comment to the new pattern or delete the line entirely to avoid misleading docs; ensure the comment near GetBenthosImage clearly shows the current registry pattern "docker.redpanda.com/redpandadata/connect".
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@internal/resources/registries/image.go`:
- Line 14: The file-level doc comment is out of date: replace or remove the
stale registry reference "// public.ecr.aws/<organization>/jeffail/" so it
matches the actual image registry used by GetBenthosImage
(docker.redpanda.com/redpandadata/connect) — update the comment to the new
pattern or delete the line entirely to avoid misleading docs; ensure the comment
near GetBenthosImage clearly shows the current registry pattern
"docker.redpanda.com/redpandadata/connect".
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: ca3d6124-d569-4d97-81f8-49b3f1dcf3d1
📒 Files selected for processing (2)
internal/resources/benthos/controller.gointernal/resources/registries/image.go
| // Format Accepted: | ||
| // ENDPOINT/ORGANIZATION/REPOSITORY:VERSION | ||
| // ghcr.io/<organization>/<repository>:<version> | ||
| // public.ecr.aws/<organization>/jeffail/benthos |
There was a problem hiding this comment.
The comment does not match the line below.
8f0403d to
bc3f1ca
Compare
There was a problem hiding this comment.
♻️ Duplicate comments (1)
internal/resources/registries/image.go (1)
14-14:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFix the incomplete registry format example.
Line 14 currently omits repository and version, so it no longer matches the accepted
registry/image:<version>format documented around it.Proposed fix
-// public.ecr.aws/<organization>/jeffail/ +// public.ecr.aws/<organization>/jeffail/benthos:<version>🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@internal/resources/registries/image.go` at line 14, The example registry string "public.ecr.aws/<organization>/jeffail/" is incomplete and should follow the documented registry/image:<version> format; update the comment to include a repository and tag (for example replace "public.ecr.aws/<organization>/jeffail/" with "public.ecr.aws/<organization>/jeffail/<image>:<version>") so the example in internal/resources/registries/image.go matches the accepted format.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Duplicate comments:
In `@internal/resources/registries/image.go`:
- Line 14: The example registry string "public.ecr.aws/<organization>/jeffail/"
is incomplete and should follow the documented registry/image:<version> format;
update the comment to include a repository and tag (for example replace
"public.ecr.aws/<organization>/jeffail/" with
"public.ecr.aws/<organization>/jeffail/<image>:<version>") so the example in
internal/resources/registries/image.go matches the accepted format.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: e778195e-3bdf-492c-b710-4f1886d67831
⛔ Files ignored due to path filters (1)
tests/e2e/chainsaw/23-benthos-module/chainsaw-test.yamlis excluded by!**/*.yaml
📒 Files selected for processing (2)
internal/resources/benthos/controller.gointernal/resources/registries/image.go
bc3f1ca to
190ceda
Compare
Signed-off-by: Sylvain Rabot <sylvain@formance.com>
190ceda to
cbfda6d
Compare
✅ Approve — automated reviewThis PR replaces the Benthos image reference with the Redpanda Connect equivalent. The previously identified issues — unqualified Docker Hub image reference, mismatched e2e test assertion, and stale comment in image.go — were all raised in prior automated and human review threads and appear to have been resolved in the current diff (the image is now fully qualified as No findings. |
NumaryBot
left a comment
There was a problem hiding this comment.
NumaryBot posted 2 new inline findings.
Summary: #463 (comment)
NumaryBot
left a comment
There was a problem hiding this comment.
NumaryBot posted 1 new inline finding.
Summary: #463 (comment)
NumaryBot
left a comment
There was a problem hiding this comment.
NumaryBot review complete: no remaining inline findings.
Resolved 1 stale NumaryBot review thread (0 fixed, 1 outdated).
Summary: #463 (comment)
No description provided.