fix: delete TopologyServiceApplication rows before services to prevent FK violation

[themavik]

Summary

Fixes #5439

When refreshing topology data from a provider (e.g., ArgoCD, Cilium), the process_topology function deletes existing TopologyServiceDependency and TopologyService records before creating new ones. However, it does not delete TopologyServiceApplication rows that reference the services being deleted.

Since TopologyServiceApplication.service_id has a foreign key to TopologyService.id without ondelete=CASCADE, the deletion of TopologyService records fails with:

ForeignKeyViolation: update or delete on table "topologyservice" violates
foreign key constraint "topologyserviceapplication_service_id_fkey" on
table "topologyserviceapplication"

Changes

1. Query service IDs first — collect all TopologyService.id values for the provider before deleting anything, so we can use IN clauses for targeted cleanup.

2. Delete TopologyServiceApplication rows — remove the service-application associations before deleting the services themselves.

3. Delete dependencies by ID — use the pre-collected service IDs with IN instead of the previous subquery through has(), which is both more explicit and avoids the need for the relationship-based filter. Also deletes reverse dependencies (where the service is the depends_on_service_id target).

4. Delete services by ID — use the same pre-collected IDs for consistency.

Test Plan

• Configure ArgoCD provider and verify topology pull completes without FK violation
• Verify topology data is correctly refreshed (old services removed, new ones created)
• Verify application associations are re-created after topology refresh
• Test with Cilium provider (also reported in [🐛 Bug]: cilium topology pull error #5517)

Assisted by Claude Opus 4.6 max thinking

Made with Cursor

[vercel]

@themavik is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[greptile-apps]

Target branch is not in the allowed branches list.