…ptsDB`

Signed-off-by: Oliver Calder <oliver.calder@canonical.com>

Added `Snap` and `App` information to requests so that prompt clients
do not have to parse apparmor labels, and because that is used in the
`StoredDecision` struct.  Also added `ResourceType` to the request so
that this information can be displayed in the prompt to the user.  The
`newRequest()` function has been modified to parse the label from
apparmor into `Snap` and `App`, and to assign a `ResourceType` of
`"file"` if `msg.Class == apparmor.MediationClassFile` (which is the
only handled case in `newRequest()` at the moment).

Also, a `newStoredDecision()` function has been added which constructs a
new `StoredDecision` struct based on the information from a given
`notifier.Request` and other information which is produced early on
during the `Set()` function.  The purpose of `newStoredDecision()` is to
be a helper function for `Set()` which create decisions with unique IDs
and sets up most of the boilerplate for the decisions.  The
`Permissions` field is left as an empty list to which `Set()` will
append each permission which is actually added to the DB, since any
which are implied by previous decisions are not added.

Signed-off-by: Oliver Calder <oliver.calder@canonical.com>

Signed-off-by: Oliver Calder <oliver.calder@canonical.com>

Signed-off-by: Oliver Calder <oliver.calder@canonical.com>

Signed-off-by: Oliver Calder <oliver.calder@canonical.com>

Signed-off-by: Oliver Calder <oliver.calder@canonical.com>

…fied

Signed-off-by: Oliver Calder <oliver.calder@canonical.com>

Previously, only the IDs of modified and deleted decisions were returned
by functions which caused those modifications (`Set()` being the primary
exported one).  These modifications and deletions can occur as the
result of pruning when a new decision overrides a previous.  However,
since stored decisions are modified immediately during pruning when a
corresponding leaf is removed from the allow tree, and the `ById` map is
immediately updated to reflect that change, before the end of the
overarching function call which results in the changes, the original
states of the modified decisions have been list, and any deleted
decisions have been removed from the storage entirely.

This commit changes that.  Now, whenever a stored decision is modified
for the first time as a result of pruning, its original state is deep
copied and stored so that it can be later returned to the caller.

As this is more complicated than simply returning the IDs of changed
decisions, some refactoring was done in an attempt to reduce duplicate
code and increase modularity.  Some helper functions were also exported
for testing.

Still TODO: now that the original state of changes decisions are stored,
use that to roll back changes to other decisions if/when an error
occurs.

Signed-off-by: Oliver Calder <oliver.calder@canonical.com>

… decision storage -- WIP

Signed-off-by: Oliver Calder <oliver.calder@canonical.com>

Signed-off-by: Oliver Calder <oliver.calder@canonical.com>

Signed-off-by: Oliver Calder <oliver.calder@canonical.com>