[checkmk-commits] [tribe29/checkmk] 492b40: 15220 FIX time_period: put endpoint now returns 20...

Branch: refs/heads/2.2.0 Home: https://github.com/tribe29/checkmk Commit: 492b409973194c9e7488240f359cb1d45d9f9579 https://github.com/tribe29/checkmk/commit/492b409973194c9e7488240f359cb1d45… Author: Gav <gavin.mcguigan(a)tribe29.com> Date: 2023-02-23 (Thu, 23 Feb 2023) Changed paths: A .werks/15220 M cmk/gui/plugins/openapi/endpoints/time_period.py M tests/unit/cmk/gui/plugins/openapi/test_openapi_time_period.py Log Message: ----------- 15220 FIX time_period: put endpoint now returns 200 with edited time period config The time period put endpoint previously returned a 204 and no data response. This werk is a fix to return the time period object along with a status code of 200 to align with our other put endpoints. Scripts that use the REST API should be adjusted accordingly. Change-Id: I291636bdc3edd865854d8642537ef63352d282f5 Commit: 62e91e14067293b60e537c2de25fa83eb861c876 https://github.com/tribe29/checkmk/commit/62e91e14067293b60e537c2de25fa83eb… Author: Gav <gavin.mcguigan(a)tribe29.com> Date: 2023-02-23 (Thu, 23 Feb 2023) Changed paths: A .werks/15373 M cmk/gui/wato/pages/timeperiods.py Log Message: ----------- 15373 FIX time_period: disallow builtin timeperiod as the exclude option This werk fixes an issue where the user could via the gui interface, select the builtin time period 24X7 as the timeperiod to exclude in a custom time period. This is no longer possible. Change-Id: Ied6816ee22ee2f96634e45973f76bfeb571b9d2a Compare: https://github.com/tribe29/checkmk/compare/aca61e05dff9...62e91e140672