Almost reopened bug 508417 to cover this, but I think this is subtly different. For 10.0b5, I was in a rush and cut-n-pasted the pushsnip command from the release notes when I meant to run backupsnip. pushsnip should guard against this by requiring an additional user confirmation before proceeding. We should of course allow for a flag to override the confirmation when being run from automation.
Found in triage.
We can add -f parameter to suppress user confirmation to be used by automation.
I doubt we'll get to this before Balrog is in production for releases.