Have logs for UI sensitive operations
Hi Benjamin, As I see more and more UI operations are added, and some to be added.
I think could be good to have some simple logs for operations like:
- User removed a client (and with which options used, like: deleted certs, files, etc)
- User add client (and which options used)
- User add/modify/delete template
- User perform backup/restore (and options used)
I think this could be something very simple, just creating a class/def and adding the logging to some "audit.log" file. Also could be simple to open that file in plain text in the web UI to watch it from UI too. (Just thinking in some pythonic ways too: if it is already logging in main log, could we decorate that function and in the def used to decorate have some flag to identify those messages that also should go to 'audit.og' like a simple flag in defs that are sensitive)
Ofcourse I understand that every change means: more time to spend doing, testing, maintaining, so I understand it could take time to implement or could be never implemented. But I think this is good idea, so I'm openning the issue to see what happens.
Anyone else thinks it is good idea? Add karma to the issue please.