SyncTriggerType::Webhook exists as an enum value but is never constructed. Supporting it means an inbound webhook receiver: the external provider (e.g. S3 event notifications, GCS Pub/Sub) calls our server to trigger a sync.
Scope
- Public receiver endpoint, e.g.
POST /webhooks/connections/{id}
- Per-provider signature verification (S3/GCS/Azure each differ)
- Payload parsing then enqueue a
ConnectionSyncJob with trigger_type = Webhook
Why deferred / low priority
Not a hard requirement. A manual sync via the existing authenticated API (POST /connections/{id}/sync/) already fetches all new data on demand, which covers essentially the same use case without the added attack surface of a public receiver plus per-provider signature handling.
Revisit only if push-based, near-real-time sync becomes a concrete requirement.
Tracked from docs/connection-sync-gaps.md (#5).
SyncTriggerType::Webhookexists as an enum value but is never constructed. Supporting it means an inbound webhook receiver: the external provider (e.g. S3 event notifications, GCS Pub/Sub) calls our server to trigger a sync.Scope
POST /webhooks/connections/{id}ConnectionSyncJobwithtrigger_type = WebhookWhy deferred / low priority
Not a hard requirement. A manual sync via the existing authenticated API (
POST /connections/{id}/sync/) already fetches all new data on demand, which covers essentially the same use case without the added attack surface of a public receiver plus per-provider signature handling.Revisit only if push-based, near-real-time sync becomes a concrete requirement.
Tracked from docs/connection-sync-gaps.md (#5).