Description:

Today, Intelligent Search receives create and update events from Core but has no deletion support. If a packet is deleted from Core, its data stays indexed and searchable in ITGS — a direct DATA violation.

This feature adds deletion support to ITGS so that when Core deletes a packet, the corresponding search index entry is also removed and Core receives a confirmation before it proceeds.

What ITGS needs to build:

Accept delete requests — receive one delete message per packet from Core via Service Bus. Each message contains the packet reference to be removed from the index.

Send confirmation back to Core — after successfully removing the document from the index, ITGS must send a positive confirmation back to Core. Core will not delete its own records until this confirmation is received. If ITGS does not confirm within the timeout window, Core marks the deletion as FAILED and retries.

Ignore update events for deleted packets — once a packet is flagged for deletion, ITGS must not re-index it if a stale update event arrives before the delete is processed.

What gets deleted: The full search index document for the packet — all indexed fields, metadata, and attachments held in ITGS.

What does not get deleted by ITGS: Core DB records, Warehouse data, blob files, Marketplace data. Those are handled by other features in this epic.

Dependency: Feature 1 (Packet Group Deletion Engine) must be complete.

Belongs to EPIC: Data Deletion — Packet Purge Framework [https://feedback.enate.net/feature-request/p/data-deletion-packet-purge-framework]