[overlord-issues] [JBoss JIRA] (SRAMP-539) Content update of artifact is not part of audit history
Eric Wittmann (JIRA)
issues at jboss.org
Fri Aug 8 10:02:31 EDT 2014
[ https://issues.jboss.org/browse/SRAMP-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991762#comment-12991762 ]
Eric Wittmann commented on SRAMP-539:
-------------------------------------
While it wouldn't be *too* hard to audit an update, we should really consider removing the content update feature. The spec is a little ambiguous on the topic if I recall correctly.
> Content update of artifact is not part of audit history
> -------------------------------------------------------
>
> Key: SRAMP-539
> URL: https://issues.jboss.org/browse/SRAMP-539
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: 0.5.0.Beta3
> Reporter: Stefan Bunciak
> Assignee: Brett Meyer
>
> After updating the content of an artifact audit trail still shows only its creation:
> {code}
> Artifact Audit Trail (1 entries)
> Idx Audit Entry
> --- -----------
> 1 artifact:add by 'admin' on Aug 6, 2014 at 2:09:54 PM.
> {code}
> I suppose that content update is quite important to be part of the audit log, since meta-data update *is* part of the audit log:
> {code}
> Artifact Audit Trail (2 entries)
> Idx Audit Entry
> --- -----------
> 1 artifact:update by 'admin' on Aug 6, 2014 at 2:26:16 PM.
> 2 artifact:add by 'admin' on Aug 6, 2014 at 2:26:10 PM.
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
More information about the overlord-issues
mailing list