try new log level scheme

Author: estroz

pkg/ansible/events/log_events.go

@@ -70,7 +70,7 @@ func (l loggingEventHandler) Handle(ident string, u *unstructured.Unstructured,
 			return
 		}
 		if e.Event == eventapi.EventRunnerOnOk && debugAction {
-			logger.Info("[playbook debug]", "EventData.TaskArgs", e.EventData["task_args"])
+			logger.V(logutil.VDebug).Info("[playbook debug]", "EventData.TaskArgs", e.EventData["task_args"])
 			return
 		}
 		if e.Event == eventapi.EventRunnerOnFailed {

pkg/logutil/log_util.go

@@ -22,13 +22,17 @@ import (
 // Usage: log.V(LogVerbosity).Info(...)
 type LogVerbosity = int
 
+// The default log verbosity, given to the most important log statements,
+// is 0: log.V(0).Info(...) == log.Info(...)
+//
+// HACK: zapr doesn't calculate log levels correctly, so we must set log
+// level integers incorrectly (according to logr) for now so they map to zapr's.
 const (
-	// Default of 0. log.V(0).Info(...) == log.Info(...)
-	_ LogVerbosity = iota
+	// VDebug == -1. log.V(VDebug).Info(...) == log.Debug(...)
+	VDebug LogVerbosity = iota - 1
+	_
 	// VWarn == 1. log.V(VWarn).Info(...) == log.Warn(...)
 	VWarn
-	// VDebug == 2. log.V(VDebug).Info(...) == log.Debug(...)
-	VDebug
 )
 
 // SDKLog is the parent logger for logs generated by operator code.