MESH-316 | Supporting Unarchiving of Products

[ankitpatnaik-atlan]

Change description

When certain assets are deleted/removed from a product , the edge between the asset and product is softDeleted i.e the edge is never completely removed only the relationshipAttribute of the edge with the product is marked as DELETED. This becomes a problem when the product is archived because while archiving a product all the existing edges are softDeleted. Now there is no way to differentiate between an asset which was intentionally deleted/removed by the end user and the assets which were removed during archiving. When the product is unarchived all the softDeleted edges become ACTIVE and we end up with redundant edges. In this PR I introduced a hard deletion logic while removing edges to resolve the problem and for existing products I have added the APIs for the migration.

JIRA.

Type of change

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

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

[PRATHAM2002-DS]

Please make a list of all relationships that Product have today, we will decide on what relations we will do hard delete. Mostly for all we will do hard delete, but make a list of relationships first and then we can decide. This edgeLabelsForHardDeletion list will inlude all those lables that we decide to hard delete

[PRATHAM2002-DS]

This is not resolved yet because there will be some other relations like terms as well which will need hard delete