I had a try at this. See attached screenshot for using the "offline device" script, then the "revert" script using the request ID.

The "before/after" changelog dictionaries are not good enough to be able to revert an "UPDATE" action, but they work decently well to revert a simple delete.

In scenarios like where IP X is assigned to interface Y, and we delete IP X then interface Y, a rollback will re-create interface Y but with a different ID, so the new IP X won't be re-attached to the interface automatically.
Solving that use-case seems particularly complex as we would need to keep track of former IDs and/or dependencies.

I still think such script can be useful as long as the limitations are known, dry-run is used first, and modified data is inspected. Let me know what you think.

You can test the script over there https://netbox-next.wikimedia.org/extras/scripts/37/

Change #1066687 had a related patch set uploaded (by Ayounsi; author: Ayounsi):

[operations/software/netbox-extras@master] Add basic "revert" Netbox script

https://gerrit.wikimedia.org/r/1066687

Nice work!

In T310589#10090992, @ayounsi wrote:

I still think such script can be useful as long as the limitations are known, dry-run is used first, and modified data is inspected. Let me know what you think.

I agree it probably needs some oversight/checks after, but overall I think it's a useful thing to have there.

Change #1066687 merged by jenkins-bot:

[operations/software/netbox-extras@master] Add basic "revert" Netbox script

https://gerrit.wikimedia.org/r/1066687