Skip to content

Audit plugin #95

@joepio

Description

@joepio

When we use Commits to edit resources, we can see who changed what, when. This means we can generate an audit log for every resource. And that means we can add a couple of fields to a resource:

Adding these things to resources can be (at least a little) costly. Doing this efficiently will probably involve some caching.
Not all resources will need them (versions / commits / collections, for example).

  • Should these audit items be enabled by default for all resources where they make sense?
  • Should it be a plugin (probably, yes)?
  • How do we keep things performant?
  • If a server decides that including these audit items isn't important enough, but still wants to let others access audit logs, should we provide an alternative path? Maybe a query param or HTTP header that adds these?
  • Should all of this be part of the Versioning, history, find commits from resource #42 versioning plugin?

Metadata

Metadata

Assignees

No one assigned

    Labels

    pluginShould probably be an Atomic Plugin

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions