Allow partial activation of changes
We use the automation user and a number of scripts calling the API to make changes to the checkmk environment (eg adding hosts, setting host group tags for hosts) - and want to be able to activate just those changes automatically (as they're done programmatically we know those changes are 'safe' and 'good') and ignore changes made by other users via the GUI.
Comments: 4
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
19 May, '22
Louis Wevers MergedWhen there are changes, now I only have the option to either activate or discard them all. Even if there are changes by another user. It would be nice if I could select only the changes I want to activate or discard.
-
24 May, '22
Mourad MergedAlso the changes made by automation, like dynamic host management, should not activate changes made by other users, but only their changes.
-
03 Nov, '25
Martin Hirschvogel AdminIan, I adapted the idea to reflect the actual need: partial activation of changes. The force_foreign_changes option is just a permission, and not the underlying issue.
The underlying issue is a fundamental one: only all changes can be activated in Checkmk. Not just a subset. -
03 Nov, '25
Martin Hirschvogel System"With pending changes, allow to activate / discard a selection" (suggested by <Hidden> on 2022-05-19), including upvotes (23) and comments (1), was merged into this suggestion.