I've written Python scripts like that as well, using requests delete and post actions. I went a step further and hard-coded the URLs, too. And because the main

I've written Python scripts like that as well, using requests delete and post actions. I went a step further and hard-coded the URLs, too. And because the main branch was protected, getting the script to run meant being forced to do a PR review. But it made things easier to not fuck up. The URL that's being modified is right there, in the code. The action being performed is a delete, it's in the code. Makes things slightly more inconvenient but adds extra safety checks. Its funny when the safety checks aren't enough, though. Back in the olden days, I had to drop thousands of records from a prod database because they were poisoning some charts. Well, I was smart, you see. I first did a SELECT on the records I expected to be safe. I looked at the results, everything is okay, I'm in the right db and this is the right table. Then I did a SELECT of the records I wanted to delete. Only a couple thousand records, everything looks good. Now all I have to do is press the up arrow key once, modify the SELECT to DELETE, and run the command. So I pressed the up arrow key but nothing happened. I must've not pressed it hard enough to register so I pressed it again and it worked. I see the SELECT command, change it to delete, run it, aaaand it deleted hundreds of thousands of records. What must've happened is there was a bit of lag and all my up arrows registered at once, taking me back to the select command where I looked at the good records. Obviously I wasn't being safe enough, because I should've double checked the DELETE command I was about to run. But I thought I was being safe enough. I had done a backup before all that, so everything was fine. But I'm still traumatized like 10 years later. I quadruple check commands I'm about to run that will affect things in a major way.