Add ability to indicate unstructured STDERR trace level
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
Currently, when a command resource is run and there is unstructured text sent to STDERR, we default to trace since we don't know if it contains sensitive information. It would be useful in the resource manifest to indicate the default trace level for unstructured STDERR content so that it can be a warn or info, for example.
Proposed technical implementation details (optional)
No response
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.
Research direction
No files or tests are named. Start by locating command-resource STDERR handling and resource-manifest parsing, then determine how a configurable default trace level should flow through the existing logging behavior. Done means a manifest can select warn or info for unstructured STDERR instead of always defaulting to trace, with coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100