Comment 9 for bug 1508115

> I'm going to pretend I didn't just read that abandon/adopt stuff

Ha! To be fair, at the time it seemed mildly preferable to figuring out the convoluted StackUpdate code, e.g

 - _process_new_resource_update doesn't only process new resources, it can either update in place, or raise UpdateReplace which results in creating a new resource, with a subsequent unfathomable dance exchanging stacks and resources.

 - _process_existing_resource_update - appears to only handle the case where a resource needs to be removed?!

Anyway, my point is whichever way you go, figuring this out is hard so contemplating per-resource abandon wasn't *that* insane of an idea (well, maybe it was, given that it doesn't work, but anyway..)