Summary
We've built a Python Dynamic Plugin for Redpanda Connect that integrates
Bright Data's web intelligence APIs as native pipeline processors.
What it does
The plugin exposes four Bright Data operations as a single brightdata
processor:
- Web Unlocker — fetch any webpage, bypassing anti-bot protection
- SERP — Google search results retrieval
- Web Scraper — structured data extraction from pre-built scrapers (e.g. Amazon, LinkedIn)
- Dataset — query Bright Data's maintained datasets
Architecture
- Python Dynamic Plugin (gRPC subprocess), built on the
redpanda-connect
Python SDK
- Runs in Redpanda Connect's streams mode, supporting multiple simultaneous
pipelines
- Async operations (Scraper, Dataset) handle trigger → poll → retrieve
automatically
- Built-in retry logic with exponential backoff
Status
What we need from the Redpanda team
We'd like guidance on:
- The certification process and requirements for community plugins,
specifically Python Dynamic Plugins
- Whether Python Dynamic Plugins follow the same certification path as
Go-native connectors described in CONTRIBUTING.md, or a different process
- Where in the repo structure / documentation this should be referenced
- Any naming conventions or manifest standards we should follow
- Review process and timeline expectations
Happy to share the full functional/technical specs for review.
Thanks!
Summary
We've built a Python Dynamic Plugin for Redpanda Connect that integrates
Bright Data's web intelligence APIs as native pipeline processors.
What it does
The plugin exposes four Bright Data operations as a single
brightdataprocessor:
Architecture
redpanda-connectPython SDK
pipelines
automatically
Status
What we need from the Redpanda team
We'd like guidance on:
specifically Python Dynamic Plugins
Go-native connectors described in CONTRIBUTING.md, or a different process
Happy to share the full functional/technical specs for review.
Thanks!