Add backup:delete command
Proposed behavior
Remove backup by date. This would be the counterpart to backup:create
Listed backups from backup:list are files, database, and code and are listed by filename and date. Since a backup include all three files—as listed in the Dashboard—remove by date or some other ID might be good options.
Use Case
If there were backups that contained undesirable configurations, code, or files.
Added to Jira AL-888
Let me second thomas-thackery's suggestion.
+1 for all the reasons mentioned in the use case.
+1
Updated name to backup:delete because Terminus remove commands are non-destructive and delete commands are
Adding a +1 for this.
I was just searching for the existence of the option to delete Pantheon backups, in my case I wanted to ensure it doesn't exist to reduce possible ways a malicious actor could damage a site and make it harder to restore. I understand the initial request (and might even need that some day) but I think it can also be risky in case someone gets unauthorized admin access and breaks the site on purpose and deletes all recent backups.
I was just searching for the existence of the option to delete Pantheon backups, in my case I wanted to ensure it doesn't exist to reduce possible ways a malicious actor could damage a site and make it harder to restore. I understand the initial request (and might even need that some day) but I think it can also be risky in case someone gets unauthorized admin access and breaks the site on purpose and deletes all recent backups.
@olivierbouwman I understand your concern. In my case, there was a PDF that had to be deleted from a site because it displayed sensitive information in an image. We could remove the file from the site but there was no recourse with regards to removing that file from all backups or removing any backups that contained the information.
I am trying to make my website GDPR compliant, I think I need the ability to delete database backups when somebody requests that their information be deleted ("Right to Forget"). Without this capability I need to wait 1-6 months for the database to "age out". Perhaps there is an alternative?