Documentation for Pipeline triggers note that deleted Triggers which do not have 'force delete' enabled will result in a soft-deleted state. This means you're unable to reuse that identifier throughout the soft-delete period (6 months), worse is that you have to create a service ticket if you need to reuse a deleted identifier as you'll be unable to find where that resource is (the CLI and REST calls both expect a pipeline provided and deleted triggers are no longer attached to the pipelines)

Documentation also notes that to avoid this problem you have to globally allow force delete on resources. This seems problematic as it could mistakenly cause more issues if users delete items accidentally whilst the flag is enabled. Instead - I'd love to see a resource management inventory

The Resource Management inventory system should be available for administrators which lets you view items that exist and have been soft-deleted. It should allow permitted users to force delete resources in soft-delete states and it should also allow permitted users to restore soft-deleted items that were mistakenly deleted.

A wonderful reference would be GCP's resource manager and how it manages projects. It allows users to shutdown projects (soft delete) view soft deleted projects and restore soft deleted projects.

Thank you for your consideration!