Currently, when a pipeline is deleted in the Harness UI, it is permanently removed unless it was version-controlled via GitX or the YAML is recoverable through the audit trail. This creates friction for UI-based users who may accidentally delete pipelines and have no direct way to restore them. A “Trash” or “Recycle Bin” feature at the project level would address this gap by temporarily storing deleted pipelines (and potentially other resources) for a configurable period before permanent deletion. This would give teams, especially centralized platform teams, more control and flexibility in managing pipeline lifecycle and recovery. Key Benefits: Prevents accidental permanent loss of pipelines Reduces reliance on external version control or audit log recovery Offers a familiar and intuitive recovery workflow Improves module usability for UI-first users Sample Use Case: A user deleted a pipeline that was later needed for investigation. Since it was not Git-backed, the team had no easy way to retrieve it. A Trash folder would have enabled a simple restore action, minimizing disruption and avoiding the need to recreate logic from scratch.
