Actions
Bug #26973
closed
Rollback event log endpoint has the wrong HTTP method
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
User visibility:
Effort required:
Very Small
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
The internal endpoint has a GET method for a modification, it should be POST instead
Files
Updated by Clark ANDRIANASOLO 24 days ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO 24 days ago
- Status changed from In progress to Pending technical review
- Pull Request set to https://github.com/Normation/rudder/pull/6401
Updated by Clark ANDRIANASOLO 24 days ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|d1261ba00adbec13450948a808871d458024e01c.
Updated by Clark ANDRIANASOLO 23 days ago
It is now with POST method : 
For the authz definition, the previous user with admin read can not rollback an event log :
2025-05-28 17:54:48+0200 WARN api-processing - User 'adminread' is not authorized to access API 'eventFilterDetails 2025-05-28 17:54:48+0200 INFO api-processing.response-error - "User 'adminread' is not authorized to access API 'eventFilterDetails"
Updated by Clark ANDRIANASOLO 23 days ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ 16 days ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.7 and 8.3.2 which were released today.
Updated by Clark ANDRIANASOLO 12 days ago
- Related to Bug #27051: Event logs rollback does not do any action added
Actions