fix: bug to allow log_verbosity be set to DEBUG, WARN, and WARNING (#98)

* fixed bug to allow log_verbosity be set to DEBUG, WARN, and WARNING

* removed WARN logging verbosity option

* adjusted for logging verbosity options

* add to changelog

* added fix log verbosity issue to changelog

.changelogs/1.0.5/98_fix_log_verbosity_opts.yml

@@ -0,0 +1,2 @@
+fixed:
+  - Fix allowed values (add DEBUG, WARNING) for log verbosity. [#98]

README.md

@@ -133,7 +133,7 @@ The following options can be set in the `proxlb.conf` file:
 | `service`| daemon | 1 | Run as a daemon (1) or one-shot (0). (default: 1, type: bool) |
 | | schedule | 24 | Hours to rebalance in hours. (default: 24) |
 | | master_only | 0 | Defines is this should only be performed (1) on the cluster master node or not (0). (default: 0, type: bool) |
-| | log_verbosity | INFO | Defines the log level (default: CRITICAL) where you can use `INFO` or `CRITICAL` |
+| | log_verbosity | INFO | Defines the log level (default: CRITICAL) where you can use `DEBUG`, `INFO`, `WARNING` or `CRITICAL` |
 | | config_version | 3 | Defines the current config version schema for ProxLB |
 
 An example of the configuration file looks like:

proxlb

@@ -190,7 +190,7 @@ def __validate_config_content(proxlb_config):
         'vm_balancing_mode_option': ['bytes', 'percent'],
         'vm_balancing_type': ['vm', 'ct', 'all'],
         'storage_balancing_method': ['disk_space'],
-        'log_verbosity': ['INFO', 'CRITICAL']
+        'log_verbosity': ['DEBUG', 'INFO', 'WARNING', 'CRITICAL']
     }
 
     for string_val in validate_string_options: