Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2899

...

Have dao methods for creating and retrieving row(s) from aforementioned table.Questions on models changes:

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


what sort of filters should be allowed? pdpGroup, policy name and version and a timestamp limit (until that timestamp).

even with the timestamp, should we have a record limit? what number would be appropriate?

could it also be a filter? have specified a default limit (i.e 50 records) but can be informed on usage.

wonder if we could use a different term than "Tracker"? That term is already used within PAP with a different meaning

suggestions: PdpPolicyDeploymentAudit or PdpDeploymentAudit

Does the table need to be cleaned up at times?

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-3328

As for clean up, we might set a timelife for the audits related to deleted policies/groups. Ram Krishna Verma Ajith Sreekumar what are your thought on that?

policy-pap:

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

...

  • there are two methods - trackDeploy and trackUndeploy - where the call for new method(s) would be added
  • have a map list of trackers audit (similar to create/update groups)
  • the new method(s) would create a track object and add to a trackMap an auditList for when the updateDb method is called

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
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyPOLICY-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?