We're using the API to tear down workers but their KV bindings are not being torn down with them.

This leads to a deleted worker but its KV namespace hangs around:

await cf.workers.scripts.delete(script, { account_id })

await cf.workers.scripts.delete(script, { account_id })

await cf.workers.scripts.delete(script, { account_id })

await cf.workers.scripts.delete(script, { account_id })

How can we cascade delete the KV namspace?

Walshy•5/3/24, 1:27 PM

You can check the bindings I guess before delete and then delete those namespaces?

jasonkuhrtOP•5/3/24, 1:32 PM

Yeah doing that manually, now, should work, but there is a "force" option and I'm wondering if that would cause cascade?

kian•5/3/24, 3:35 PM

I'm not aware of any cascade delete for bindings in the API

Walshy•5/3/24, 5:46 PM

Yeah nothing in the API. We don't like touching other resources (especially deletes). Very very easy to go wrong