A BitBucket repository-admin can delete/remove/archive/strike a "deployment" entity, so that they can have a clean deployment history if someone accidentally commits changes to the repo's Pipelines (bitbucket-pipelines.yml) that erroneously indicates something was deployed somewhere.

Customer use case:

I imagine this is a somewhat frequent occurrence, but only when teams are setting up and/or modifying their Pipelines config. For my current scenario, I just want to remove the deployment metadata associated with some of these "dummy deployments", which didn't actually deploy anything and were instead just the result of a starter pipelines template.

I don't wish to modify the build history, as that is a representation of pipeline runs. I want the ability to strike a "deployment" that is associated with a pipeline run, so that I can clean up any erroneous "deployments".