[checkmk-commits] [tribe29/checkmk] dc055b: 11938 REST API: make optimistic locking via ETag c...

Branch: refs/heads/2.0.0 Home: https://github.com/tribe29/checkmk Commit: dc055b8e4c89236fd14289e6d3c88c0fd41e2289 https://github.com/tribe29/checkmk/commit/dc055b8e4c89236fd14289e6d3c88c0fd… Author: Christoph Rauch <christoph.rauch(a)tribe29.com> Date: 2021-02-26 (Fri, 26 Feb 2021) Changed paths: A .werks/11938 M cmk/gui/plugins/config/base.py M cmk/gui/plugins/openapi/restful_objects/constructors.py M cmk/gui/plugins/openapi/restful_objects/decorators.py M cmk/gui/plugins/wato/check_mk_configuration.py A tests/unit/cmk/gui/plugins/openapi/test_openapi_etags.py Log Message: ----------- 11938 REST API: make optimistic locking via ETag configurable When multiple HTTP clients want to update an object at the same time, it can happen that the slower client will overwrite changes by the faster one. This is commonly referred to as the 'lost update problem'. To prevent this situation from happening, Checkmk's REST API does 'optimistic locking' using HTTP ETag headers. In this case the Object's ETag has to be sent to the server with a HTTP If-Match header. This behavior can now be deactivated, but this will allow the 'lost update problem' to occur. Change-Id: I3cdd52c349cba8d0f532addd921af89639cce640