layer5io / layer5io/learn-layer5
Ensure that all SMI Conformance logs and errors are funneled to Meshery's stdout
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 72
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
@nveenjain are we using the "github.com/sirupsen/logrus" package here? // @anandrkskd
@nveenjain I think you were saying that use of kuttl's logger is best for the use case here, is that right?
Originally posted by @leecalcote in https://github.com/layer5io/learn-layer5/pull/15/files
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 the SMI Conformance logging and error paths in this Go repository, then review the referenced discussion about logrus and kuttl's logger. Done means that all SMI Conformance logs and errors are emitted through Meshery's stdout, but the issue does not name files or tests to guide verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100