[checkmk-commits] [Checkmk/checkmk] 471a11: Activate changes no longer breaks remote site

Branch: refs/heads/master Home: https://github.com/Checkmk/checkmk Commit: 471a115eec84ea96cf0cd5e01bc091fcff9895f5 https://github.com/Checkmk/checkmk/commit/471a115eec84ea96cf0cd5e01bc091fcf… Author: Andreas Boesl &lt;andreas.boesl(a)checkmk.com&gt; Date: 2023-08-19 (Sat, 19 Aug 2023) Changed paths: M cmk/gui/watolib/activate_changes.py Log Message: ----------- Activate changes no longer breaks remote site Change-Id: If3b32b18a9b821c55aef6ef73a957bf95eda0286 Commit: 5ccd270d862510ad590bc2315e77fdb8d1c7a123 https://github.com/Checkmk/checkmk/commit/5ccd270d862510ad590bc2315e77fdb8d… Author: Andreas Boesl &lt;andreas.boesl(a)checkmk.com&gt; Date: 2023-08-19 (Sat, 19 Aug 2023) Changed paths: M cmk/gui/htmllib/html.py M cmk/gui/wato/pages/activate_changes.py M cmk/gui/watolib/activate_changes.py M cmk/gui/watolib/changes.py M web/htdocs/js/modules/forms.ts A web/htdocs/themes/facelift/images/icon_no_revert.svg A web/htdocs/themes/facelift/images/icon_revert.svg Log Message: ----------- Setup: Introduced add_change option to forbid the use of 'discard change' Change-Id: I1a0c5df0847cde489c6d5d7f65f0e6324ca26e57 Commit: 2fc943d0777921051209e472a9c0e943c8202ee3 https://github.com/Checkmk/checkmk/commit/2fc943d0777921051209e472a9c0e943c… Author: Andreas Boesl &lt;andreas.boesl(a)checkmk.com&gt; Date: 2023-08-19 (Sat, 19 Aug 2023) Changed paths: A .werks/14208 M cmk/gui/wato/pages/host_rename.py M cmk/gui/watolib/host_rename.py M cmk/gui/watolib/hosts_and_folders.py Log Message: ----------- 14208 Setup: Renaming a host on a remote site no longer requires no pending changes in the central site You can now rename a host at the remote site even if there are pending changes at the central site. This restriction has been removed because some setups with hundreds of sites rarely had an empty pending changes list. Also, sometimes users weren't allowed to see all sites - so they couldn't see other users' pending changes. However, this introduced another restriction: You can not use the <tt>Discard changes</tt> feature after a host renaming operation, until the next <tt>Activate Changes</tt> of the central site. The reasoning behind this is that the rename operation is something which cannot be discarded, because the operation was already executed on the remote site. The hosts' autochecks, historic data, rrd were already rewritten. Change-Id: I5bb947c381fcb4e27e845e342a1595f522877cb5 Compare: https://github.com/Checkmk/checkmk/compare/66cfeada804f...2fc943d07779