Undeploy pipeline before deletion to stop agents

[TerrifiedBug]

No description provided.

[greptile-apps]

Greptile Summary

This PR adds a graceful undeploy step before pipeline deletion. When a deployed pipeline is deleted, it now sets isDraft: true and deployedAt: null before removing the database record, ensuring agents stop the pipeline on their next config poll rather than continuing to run a deleted pipeline.

Key Changes:

• Added conditional undeploy update before prisma.pipeline.delete() in the delete mutation
• Checks existing.deployedAt to only undeploy if the pipeline was actually deployed
• Maintains existing authorization (withTeamAccess("EDITOR")) and audit logging (withAudit)

Implementation Notes:

• The undeploy and delete operations are not wrapped in a transaction, which is acceptable - if deletion fails, the pipeline remains in an undeployed state that can be manually recovered
• Agents polling between undeploy and delete will gracefully stop the pipeline and handle the subsequent missing pipeline on the next poll

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• Simple, focused change that addresses a real operational issue. The code follows established patterns, uses proper middleware (withTeamAccess, withAudit), and includes a clear explanatory comment. The undeploy-before-delete approach is sound and the edge cases (non-deployed pipelines, system pipelines) are already handled by existing checks.
• No files require special attention

Important Files Changed

Filename	Overview
src/server/routers/pipeline.ts	Added undeploy step before deletion to gracefully stop agents - clean implementation with proper authorization and audit logging

_{Last reviewed commit: bd5b8d4}

[TerrifiedBug]

https://github.com/user-attachments/assets/6c1003be-9e54-46b3-8bc3-1ccfe48cbbdd
https://github.com/user-attachments/assets/207e5f17-eca4-490a-abfe-f1d86402840f
https://github.com/user-attachments/assets/c7f7e5be-df2a-4877-b716-b125a343f902