Update Classification add/delete behaviour

[aarshi0301]

Change description

JIRA :

https://atlanhq.atlassian.net/browse/PLT-367

Current behaviour :

Example :

If 3 tags are added to single entity

there use to be three CLASSIFICATION_ADDED events for that entity

If 3 tags are added to two entities

there use to be six CLASSIFICATION_ADDED events (3 events per entity)

Desired Behaviour:

Example :

If 3 tags are added to single entity

there will be one CLASSIFICATION_ADDEDevent for that entity

If 3 tags are added to two entities

there will be two CLASSIFICATION_ADDEDevent (1 event per entity)

Area of Impact :

1. Audit events
2. Kafka events
3. AuditSearch API (consumed across multiple teams)

Proposed changes to embed desired behaviour :

• Classification_added

  Current behaviour
  i. We have detail object that contains tag information.

  Proposed behaviour

  1. Representing Future classification_added event
     i. detail object will be empty.
     ii. add key classificationsDetails object to show current tags
     removed from entity.

  2. Representing Past data classification_added event
     i. detail object contains tag information.
     ii. classificationsDetails object will be empty

• Classification_deleted event

  Current behaviour :
  i. We have detail object that contains tag typeName only.

  Proposed behaviour

  1. Representing Future classification_deleted event
     i. detail object will be empty.
     ii. add key classificationsDetails object to show current tags
     removed from entity.
  2. Representing Past data classification_added event
     i. detail object contains tag information.
     ii. classificationsDetails object will be empty.

Type of change

• Bug fix (fixes an issue)
• New feature (adds functionality)

Related issues

Fix #1

Checklists

Development

• Lint rules pass locally
• Application changes have been tested thoroughly
• Automated tests covering modified code pass

Security

• Security impact of change has been considered
• Code follows company security practices and guidelines

Code review

• Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached as necessary
• "Ready for review" label attached and reviewers assigned
• Changes have been reviewed by at least one other contributor
• Pull request linked to task tracker where applicable