Replies: 1 comment 2 replies
|
Hey @shyam-cb! Usually, integrations start as community-maintained, with the option to move them into the |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'd like to propose adding prefect-couchbase as an official Prefect integration under
src/integrations/prefect-couchbase. It provides a Prefect credentials block and a small connector around the official Couchbase Python SDK, so flows can store Couchbase connection details as a block and run common operations (upsert, get, remove, SQL++ query, ping) without hand-rolling SDK setup in every flow.Right now there's no first-party way to connect Prefect to Couchbase (or Capella), so users manage credentials and connections manually. This would give them the same block-based, load-by-name experience as integrations like prefect-snowflake and prefect-redis.
It's already built and working: password and certificate auth, context-managed connection lifecycle, unit + live integration tests at 100% coverage, plus docs and runnable examples. Current repo: https://github.com/couchbase-ecosystem/couchbase-prefect
Would you accept this into
src/integrations, and is there anything you'd want changed before I open a PR?All reactions