Log the command line error before generating support bundles
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What would you like to be added**:
We should log the error message first before going into the support bundle step when CLI fails.
**Why is this needed**:
Generating support bundle is a relatively time consuming task. It is launched whenever CLI fails. Currently the actual CLI error message is only printed out after support bundle generation. Many times as users we simply want to see the error and iterate accordingly. Moving the error message up so that user can have quick feedback and does not need to rely on relatively time consuming support bundle generation.
Contributor guide
Research direction
Trace the CLI failure path and the support bundle generation step. Confirm where the CLI error is currently emitted, then make the error visible before the relatively time-consuming support bundle work begins. Verify the behavior by exercising a failing CLI command and confirming the error appears immediately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100