-
Notifications
You must be signed in to change notification settings - Fork 71
Closed
Description
Summary
Deliver the source-smoke-test, source-pyairbyte (universal source), and destination-pyairbyte (universal destination) connectors as a test harness in the airbyte-ops-mcp repo, rather than registering them as official connectors in the Airbyte monorepo.
Background
- PyAirbyte PR #969 adds the universal source/destination and smoke-test source to PyAirbyte. CI is green (22/22 checks passing). Awaiting human review.
- PyAirbyte PR #982 (merged into feat(connectors): add universal source and destination using PyAirbyte #969 branch) added the smoke-test source with 15 predefined scenarios for destination regression testing.
- Monorepo PR airbytehq/airbyte#74058 was the companion PR to register
source-smoke-testas an official connector in the Airbyte registry. This has been closed in favor of this issue — the plan is to first deliver the connectors as a test harness in the ops repo, and revisit official connector registration after they've proven stable. - Closes #981 scope is narrowed to the test harness delivery.
Remaining work
1. Merge PyAirbyte PR #969
PR is CI-green. Outstanding bot suggestions (deferred to human reviewer):
- SQL identifier quoting: schema/table names are f-string interpolated into raw SQL without quoting (breaks on stream names with dashes, dots, spaces)
- Raw exception text:
check()returnsrepr(exception)which could expose config details - Buffer flush threshold: no configurable threshold; flushes only on STATE messages
2. Integrate into airbyte-ops-mcp as test harness
Once #969 is merged and released, integrate the smoke-test source and universal destination into the ops repo as a test harness for destination regression testing.
3. Future: Register as official connectors
After the test harness has proven stable, revisit registering these as official connectors in the Airbyte monorepo (see closed PR airbytehq/airbyte#74058 for prior work).
Requested by
Aaron ("AJ") Steers (@aaronsteers)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Give feedbackNo fields configured for issues without a type.