The use case:
managed/A has 1:many relationship to managed/B. managed/A has an attribute "status". managed/B has an attribute "status".
A managed/A resource "a1" has a relationship to many managed/B resources [b1, b2, .., bn]. When "a1.status" is change to "REMOVED", the business logic is to set "status" to "REMOVED" for all [b1, b2, .., bn].
Currently, we can retrieve all A->B relationships from "a1", and iterated and update each resource in [b1, b2, .., bn]. If the list [b1, b2, .., bn] is large, for example, in terms of thousands, then this iteration/update could have performance impact.
The desired outcome is to have a bulk UPDATE/PATCH API that accepts and updates a list of resources.