In order to scale well for common actions like listing several resources of the same resource type and the same action, audit and authorize should be able to take multiple resources. several: Resource attrs, parents and children objects. Without this it would cause significant thrash in general; If I list 1000 of the same resource but the calling entity is only allowed certain ones. Being able to request multiple would eliminate a lot of storage overhead, and optimize compute use if it's the same resource type. I think the request should change to only take an array of resources. There really isn't any need to have a single and multiple when you can just pass a single. It would be purely for semantics and doesn't make sense.
In order to scale well for common actions like listing several resources of the same resource type and the same action, audit and authorize should be able to take multiple resources. several: Resource attrs, parents and children objects. Without this it would cause significant thrash in general; If I list 1000 of the same resource but the calling entity is only allowed certain ones. Being able to request multiple would eliminate a lot of storage overhead, and optimize compute use if it's the same resource type. I think the request should change to only take an array of resources. There really isn't any need to have a single and multiple when you can just pass a single. It would be purely for semantics and doesn't make sense.