suppress logging from repo server

[krancour]

@alexmt you might be the best person to review this.

This is a prereq for akuity/kargo#951

[netlify]

✅ Deploy Preview for docs-kargo-render-akuity-io ready!

Name	Link
🔨 Latest commit	1730c4f
🔍 Latest deploy log	https://app.netlify.com/sites/docs-kargo-render-akuity-io/deploys/6536fd5a94b5ed0008c5d684
😎 Deploy Preview	https://deploy-preview-206.bookkeeper.akuity.io
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (2c78951) 38.28% compared to head (1730c4f) 38.28%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #206   +/-   ##
=======================================
  Coverage   38.28%   38.28%           
=======================================
  Files          19       19           
  Lines        1157     1157           
=======================================
  Hits          443      443           
  Misses        697      697           
  Partials       17       17           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jessesuen]

In addition to surpressing logging as a default, which I think we should do, another common technique that I think we should do is logging to stderr instead of stdout. The parseable output would continue going to stdout. In fact, this is what kubectl does.

So you could do:

kubectl get pods -o json -v=6

The pod json would be to stdout, but the log messages would go to stderr:

I1023 15:37:26.181218   12126 loader.go:374] Config loaded from file:  /Users/jesse/.kube/config
I1023 15:37:26.937120   12126 round_trippers.go:553] GET https://mycluster.com/api/v1/namespaces/default/pods?limit=500 200 OK in 749 milliseconds

I'll approve this PR for the log level reduction. Feel free to create a different issue or PR for switching to stderr for log output.

[krancour]

another common technique that I think we should do is logging to stderr instead of stdout. The parseable output would continue going to stdout

I had that thought as well. Since you like it also, yes... I'll open an issue for it.