Clarified for log levels which default values apply

Author: m-mohr

CHANGELOG.md

@@ -11,6 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `GET /file_formats`: Base paramater on top of normal JSON Schema, not Process JSON Schema
 - `PATCH /services/{service_id}` and `PATCH /jobs/{job_id}`: Explicitly allow updating back-end specific properties (as in `POST`)
 - `GET /services/{service_id}` and `GET /jobs/{job_id}`: Explicitly allow listing back-end specific properties (as provided in `POST`)
+- Clarified for log levels which default values apply
 
 ## [1.2.0] - 2021-05-25
 

openapi.yaml

@@ -5895,7 +5895,8 @@ components:
         The order of the levels is as follows (from low to high severity): `debug`, `info`, `warning`, `error`.
         That means if `warning` is set, the back-end will only store log entries with the level `warning` and `error`.
 
-        The default minimum log level is `info`. Users need to specifically set this property to `debug` to get *all* log entries.
+        The default minimum log level is `info`.
+        Users need to specifically set this property to `debug` to capture *all* log entries.
         It is RECOMMENDED that users set the level at least to "warning" in production workflows.
       type: string
       enum:
@@ -6626,7 +6627,7 @@ components:
           - warning
           - info
           - debug
-        default: info
+        default: debug
     service_id:
       name: service_id
       in: path