Open nemesifier opened 1 month ago
A revision should possibly be created if an object is saved by anything but the admin.
https://django-reversion.readthedocs.io/en/latest/api.html#creating-revisions
Additionally it might be need to use follow()
when registering a model:
https://django-reversion.readthedocs.io/en/latest/api.html#registration-api
@okraits reading the issue again, I think I forgot to specify that I meant to convey that this problem happens when modifying objects via the REST API.
Is your feature request related to a problem? Please describe.
It seems to me that changing objects via the REST API, like devices or templates , which in the admin are monitored via django-reversion, doesn't store revisions.
Therefore if a device is changed via the API, there's no way to rollback changes, nor know who changed the object.
Describe the solution you'd like
Ideally, for each model which supports reversion in the admin, we would need to add equivalent features for the REST API:
Describe alternatives you've considered There may be third party open source tools we can use, otherwise we can add our own logic in openwisp-utils and start rolling this feature out in the main modules.