Feature idea: Allow the user to define which logs to print in stdout
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go, kubernetes
- Domain
- cli, observability
Research direction
Start at the CLI path triggered when the s key is pressed, then trace how resource logs are selected and streamed to stdout. No file or test is named in the issue, so first identify the relevant CLI entry point and existing log tests. Done should provide a way to choose which resource logs appear while preserving the current behavior when no filter is configured.
Written by the indexing model from the issue text.
Description
Describe the Feature You Want
I'm currently doing TDD on a codebase which makes use of an API with a rather noisy log output. It would be nice if I could choose to only stream the log output of my tests in the terminal.
Current Behavior
All resource logs are printed to stdout when the s key is pressed in the CLI.
Why Do You Want This?
- I have a codebase (A) which calls an API (B)
- A and B both use tilt
- In A's tiltfile, I clone B into a temporary directory and include B's tilt file so that both boot up in my local kubernetes cluster
- I configure A's ConfigMap to send A's API requests to B
- A runs its tests whenever a live update happens, resulting in API calls to B.
- Tilt prints the log output of both A and B, producing a rather chaotic output
- I prefer to have a terminal with my tests running next to (or inside) my editor while doing TDD.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tilt-dev/tilt
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Tilt at scale Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100