acoustic-carpenter-78188
04/16/2026, 8:02 AMTailLogsRequest only accepts an action execution ID and attempt number, which means the service has to guess which pod to tail logs from. Adding a pod_name field allows callers to explicitly specify the target pod, which is useful when an action has multiple pods.
What changes were proposed in this pull request?
Add a pod_name field (field number 3) to TailLogsRequest in run_logs_service.proto. If not provided, the service will attempt to find the primary pod, else assume the first pod.
Regenerated all language bindings (Go, Python, Rust, TypeScript).
How was this patch tested?
Proto compilation and code generation verified.
Labels
• added
Check all the applicable boxes
• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.
• main
• #6583
• [V2] Add pod_name field to TailLogsRequest 👈
flyteorg/flyteacoustic-carpenter-78188
04/21/2026, 4:49 PM