Closed hilmarf closed 5 months ago
it's not that hard to do proper logging... is it?
The logger comes from OCM context. This is an uninitialized logger that logs to god knows what. You might as well use fmt.Println at that point.
Integration Tests for ac1b146a5d8d5d681035d681c67e342b2e578af4 run with result: Success ✅!
Integration Tests for ac1b146a5d8d5d681035d681c67e342b2e578af4 run with result: Success ✅!
Integration Tests for ac1b146a5d8d5d681035d681c67e342b2e578af4 run with result: Success ✅!
Integration Tests for ac1b146a5d8d5d681035d681c67e342b2e578af4 run with result: Success ✅!
Integration Tests for ac1b146a5d8d5d681035d681c67e342b2e578af4 run with result: Success ✅!
Integration Tests for ac1b146a5d8d5d681035d681c67e342b2e578af4 run with result: Success ✅!
@Skarlso - wouldn't that be an easy solution to simple log, where it's not possible to return errors?