External activation garbage collection

[jbockle]

I'm experimenting with integrating cosmos db with graph (gremlin) api with Orleans. I first thought maybe I could create a persistence provider for vertices or utilize a custom vertex grain base + lifecycle participation to bridge the vertex state.

The problem I'm facing, what if a dev decides to delete a bunch of vertices with something like g.V().Drop(), how do I ensure if any those vertex grains are activated, they get deactivated? I could use cosmos soft-delete + change feed processor, but is there a way to tell only specific activated grains to deactivate without calling a grain's method that would result in activating it if it wasn't already activated?