Mutation

Revisions are broken down into one or more Mutations, which track the sources of granular changes to the configuration, including automated changes, such as imperative or Triggered function invocations, addition of links, upgrades from upstream units, other update API calls, etc. This information can be used to make decisions about how future updates to specific configuration attributes should be handled, as well as providing an audit trail of both who and what changed each attribute.