Bug #25503
open
Changes on system objects should not have rollback and links in events logs
Description
When consulting event logs and searching for events on system directives and rules (e.g. the one created for system-updates campaigns), I can get a link on those objects and access a page that is supposed to be hidden for them, I can even attempt to rollback those events :
Hopefully, attempting a rollback leads to an error :
2024-09-20 10:13:47+0000 INFO api-processing.response-error - "Error when performing eventlog's rollback with id '123' <- The event log 123 don't have a matching commit ID and can't be restored"
Also the objects end up not being modifiable in the Directives and Rules pages (thanks to the API enforcing that system directives and rules are not modifiable).
We should hide the rollback section for system objects, and links should not be generated for new event logs on those objects
Files
Updated by Clark ANDRIANASOLO 4 days ago
I can also clone the directive/rule and cloning a directives ends up with a directives with the systemUpdateCampaign technique category (but with attribute isSystem to false).
However, the update campaigns page does not list the cloned campaign directive.
It would still be possible to run campaigns by changing the parameters to the cloned directive, and assign a new rule for it (via API to assign the cloned directive ID).
I think this is not supposed to be an allowed usage, and the system objects should not be visible in the directives web page, nor in the API
Updated by Clark ANDRIANASOLO 4 days ago
- Related to Bug #25518: System rules and directives details page should not have action buttons added