Comment 9 for bug 1326721

I think a concrete example of why this is needed for Juno would be helpful, e.g so we can justify the backport as strictly speaking it's both a feature and a new interface, so probably wouldn't normally be considered valid for a stable backport.

That said, if some obviously needed use-case is impossible on Juno because of this ommision, I think it's reasonable to say it's in the best interests of users to backport it (particularly if we're satisfied it's totally backwards compatible and would not adversely affect any existing users/templates on Juno.

Can anyone provide a more detailed example of where a query is needed for resource that don't have metadata associated?