feature: add temporal control-plane connect service#75
Conversation
|
Warning Review limit reached
More reviews will be available in 31 minutes and 42 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Adds a new temporal.v1.TemporalService protobuf service definition to expose the Temporal plugin’s control-plane RPC surface in the v6 Connect-RPC API layer, reusing existing replay-related message types already defined in temporal/v1/temporal.proto.
Changes:
- Introduces
TemporalServicewith RPCs for activity heartbeats, workflow/activity name introspection, workflow replay/history tooling, and API key rotation. - Adds new request/response messages for heartbeats, name listing, and API key updates, while reusing
ReplayRequest,ReplayResponse, andHistory.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
temporal.v1.TemporalServicemirroring the temporal plugin's control RPC surface for the v6 Connect-RPC layer:RecordActivityHeartbeat,GetActivityNames/GetWorkflowNames, the four workflow replay methods (reusing the existingReplayRequest/ReplayResponse/Historymessages), andUpdateAPIKey