General Description

Currently Audit can only be triggered via a manual REST call (as of the completion of PoC development work).  The goal of this feature is to provide a more systematic way of triggering when an audit occurs as well as the enhancing support of manually triggered events (eg via portal, etc).  At the completion of service orchestration, SO should publish an event to DMaaP that includes the necessary information to allow an audit to initiate.  This event will be consumed by POMBA and then evaluated to determine if an audit should occur.

 Acceptance Criteria

• SO publishes to a DMaap topic (fire and forget) at the completion of service orchestration
• Event contains the appropriate information as required by Audit flow
• Event is consumed by POMBA
• Audit is initiated and results in validation being completed on the supported artifacts/data
• Audit can alternatively be initiated by REST call

Value

Provides systematic way of triggering audits

Common assumptions

Logging as per ONAP Casablanca standards