Expected Behavior
tilt logs -f <resource> should only show logs for the specified resource, not logs from other resources.
Current Behavior
When running tilt logs -f <resource>, the output includes logs from other resources such as:
Initial Build messages from all resources
N Files Changed: [...] messages from unrelated services
Steps to Reproduce
- Start Tilt with multiple resources (e.g., service-a, service-b, service-c)
- Run
tilt logs -f service-a
- Make file changes in another service (e.g., service-b)
- Observe "Files Changed" and "Initial Build" messages from other resources appearing in service-a logs
Example output:
$ tilt logs -f service-a
Initial Build
STEP 1/1 — Deploying
Applying YAML to cluster
Objects applied to cluster:
→ service-a:service
→ service-a:deployment
DONE IN: 0.40s
Initial Build
Initial Build
Initial Build. <- not a typo, actually getting a bunch of these messages in bulk
Initial Build
Attaching to existing pod (service-a-67b887b894-xxxxx). Only new logs will be streamed.
Initial Build
6 Files Changed: [/path/to/service-b/file1 /path/to/service-b/file2 ...]
Initial Build
19 Files Changed: [/path/to/service-c/file1 /path/to/service-c/file2 ...]
Expected Behavior
tilt logs -f <resource>should only show logs for the specified resource, not logs from other resources.Current Behavior
When running
tilt logs -f <resource>, the output includes logs from other resources such as:Initial Buildmessages from all resourcesN Files Changed: [...]messages from unrelated servicesSteps to Reproduce
tilt logs -f service-aExample output: