Audit Configuration Changes

[xevix]

Large setups of Octoparts with many parts and many settings with widely used API endpoints can lead to erroneous or harmful changes, the length of time and impact of which is hard to ascertain without an auditing trail.

Example: Local contents is set on an endpoint temporarily to fix an issue, and is accidentally left turned on. It's useful to know: when was this set and by whom, to know the impact, and to get a story of what might have happened.

Might be a good candidate for the use of this: http://clarkdave.net/2015/02/historical-records-with-postgresql-and-temporal-tables-and-sql-2011/

[lloydmeta]

This is a great idea. :+1:

[seratch]

:+1: