PipedreamHQ/pipedream

[TRIGGER] Pipedream Data Store - New Key in Data Store, Updated key in Data Store

Open

#9,408 opened on 2023年12月21日

GitHub で見る
 (3 comments) (1 reaction) (1 assignee)JavaScript (7,438 stars) (5,305 forks)batch import
blockedenhancementgood first issuehelp wantedtriagedtrigger / source

説明

Describe the event source. What app is this for, and what event does the trigger correspond to? App: Pipedream Data Store

Triggers: I think this might need some development effort from the Pipedream internal team to develop subscription/webhook for datastore. Though, inittially it can be a polling source.

  • New Key in Data Store: emit event when there is a new key in a Data store. The event data should have key and value of the record in Data store
  • Updated key in Data Store: emit event when there the speicified key is updated in a Data store. The event data should have key, new value and old value of the record in Data store
  • Deleted Key in Data Store: emit event when a key deleted from a Data store. The event data should have key and value of the record in Data store

Please provide a link to the relevant API docs for the specific service / operation this trigger is tied to. https://pipedream.com/docs/data-stores/

Context Requested by a Business customer here: https://pipedream-users.slack.com/archives/CN1BUB92B/p1703118948881209

コントリビューターガイド

技術スタック
javascripttypescriptnodejs
領域
backendapi
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
blocked
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
unclear
前提条件
Node.jsPipedream basicsEvent source patterns
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
30
調査方針
The issue requests triggers for Pipedream Data Store events (new, updated, deleted keys). The Data Store docs are at https://pipedream.com/docs/data stores/. There is an assignee, so first check if they have made progress. The initial approach could be a polling source that periodically checks for changes. Look at existing Pipedream event source implementations in the repository for patterns, e.g., under 'components/'. The issue notes that webhook subscription might require internal development, so a polling solution is recommended for now.