Add scaffolding for CompleteStartedTask implementation in matching

What changed? Added scaffolding for the new IDL CompleteStartedTask implementation in matching. This endpoint will be called by the history service in order to complete a task in matching after it has been replicated in history. Why? This will allow cadence to actively delete stale tasks from matching on the passive side as these tasks are processed on the active side and replicated, avoiding the large passive side partitions and reducing task processing latency after a failover How did you test it? This implements only the scaffolding. No logic present. Potential risks Release notes Documentation Changes
cadence-workflow · Aug 27, 2024 · d917552 · d917552
1 parent c0cd4c5
commit d917552
Show file tree

Hide file tree

Showing 20 changed files with 6,846 additions and 3,408 deletions.
diff --git a/.gen/go/history/history.go b/.gen/go/history/history.go
diff --git a/.gen/go/matching/matching.go b/.gen/go/matching/matching.go
diff --git a/.gen/go/matching/matchingserviceclient/client.go b/.gen/go/matching/matchingserviceclient/client.go
diff --git a/.gen/go/matching/matchingserviceserver/server.go b/.gen/go/matching/matchingserviceserver/server.go
diff --git a/.gen/go/matching/matchingservicetest/client.go b/.gen/go/matching/matchingservicetest/client.go