Page Comparison

Summary:

Develop a solution for storing information when policies are deployed or undeployed through the PAP deploy APIs.

...

Have dao methods for creating and retrieving row(s) from aforementioned table.

models-pap

/policy-models-pap/src/main/java/org/onap/policy/models/pap/concepts/PolicyAudit.java - concept

/policy-models-pap/src/main/java/org/onap/policy/models/pap/persistence/concepts/JpaPolicyAudit.java - persistence entity

/policy-models-pap/src/main/java/org/onap/policy/models/pap/persistence/provider/PolicyAuditProvider.java - dao actions

tests and a persistence.xml file would be added to src/test

policy-pap:

have the endpoints for deploy/undeploy updated with the call for storing the process for tracking.

...

have a new endpoint to get the audit on policy (need to confirm which fields would be used for filter - assuming pdp group or policy name/version, and begin/end times)

Questions:

• How many records could this return? may want to force a limit on the record count and maximum time window. may want to require starting timestamp
  • limit set on API: 10
  • limit set on models provider: 50 (there's a validation to check if number is over models limit) - should we keep this and this range (10-50)
• Does the table need to be cleaned up at times?

  • Jira Legacy
    server System ONAP Jira serverId 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb key POLICY-3328

• what sort of filters should be allowed? 
  • none
  • pdpGroup
  • policy (name and version)
  • group and policy (name and version)
• Should still use timestamp on filter?
• Should we filter by actions? (i.e. want to see only deployments)
• Failure (result of a DEPLOY) is to be tracked as well?

...