leakprobe

Overview ¶

Command leakprobe is the other half of `scripts/leak-check.sh`: a harness that never cleans up, and the questions you ask BigQuery afterwards.

leakprobe make  <project> <schema>   create it the way a harness does, then block
leakprobe check <project> <schema>   what survived, and does it expire
leakprobe drop  <project> <schema>   remove it, and ONLY if this made it

IN GO AND NOT IN `bq`. The first version of the script shelled out, and `bq` asked for an interactive re-auth it could not get -- while every test in this repository was talking to the same project happily, because they use Application Default Credentials through the Go client. One credential path for everything that reaches a warehouse here.

IT GOES THROUGH THE SHARED HELPER rather than issuing its own statements, so a harness that stopped making its schema disposable makes this fail too. A probe with its own copy of the thing under test proves only the copy.