[API/notification] Add non-notification webhooks to support asynchronous connection status changes #33736
thearchitector
started this conversation in
Connector Ideas and Features
Replies: 1 comment
-
I almost immediatly found these docs, but the endpoint documented here does not exist in the open source API running locally in Docker. Are certain API features gated to the cloud version? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As a feature, the only way of programmatically knowing the status of your connection right now is to constantly poll the list of jobs, and check if the latest one is
running
,failed
orsucceeded
. As a model, polling as advantages, but also many disadvantages. The biggest one is that it requires a lot of unnecessary overhead (IO, persistent state, and tracking) in order to have an external (to airbyte) party know the status of some arbitrary connection's latest sync.It would be really useful if Airbyte, in addition to notifications, enabled JSON-payload subscriptions (basically just the output of the existing
getjob
API). The cherry on top would be the ability to subscribe to the start of a the latest job/sync in addition to just the success or failure of it. With that, you could get notifications about any connection's current state, be itRUNNING
,SUCCEEDED
orFAILED
.Beta Was this translation helpful? Give feedback.
All reactions