Add loglevel tracing option to tkn
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 461
- Forks
- 277
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 95
Description
--loglevel in for example the openshift client is a pretty useful option for debugging and introspectability of what the CLI is doing, it's a good example too for other people who want to talk to tekton rest api on 'how to do stuff'. For example :
Add global --loglevel option with the level as specified in oc code which would print the REST exchange and optionally have a curl constructed for easy replay,
- Add --loglevel command
- Add curl output
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
Start by locating tkn's global option handling and the code that performs REST requests, then compare the requested log levels with the referenced oc behavior. Done means a global --loglevel option traces the REST exchange and, if implemented, emits a replayable curl command; the issue checklist identifies both outcomes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100