Why 111 and not 110?

We should merge those methods (get/get_all).

If someone wants only 1 origin_metadata, (s)he should simply asks for one origin_metadata (list of 1 element).

That's what we do for most of our endpoints content, revision, etc...

Not sure why we diverge for cache_content_get/get_all endpoint.
That was either a mistake, either possibly unavoidable.
(Plus that endpoint seems to no longer be used so it should go away anyways).

To sum up, as we can avoid the duplication here, we should stick to the standard :)

indentation :)

provider/get?

missing one space tool and metadata.

time when the metadata was found?

It should probably be named origin_metadata_get_by_origin.

This probably could be merged with the method above as get_by.

a nitpick, if we take a look either at db or storage module, the pattern is inverted.

if not om:
    return None
return dict...

Maybe we could merge origin_metadata_get_by_provider_type and origin_metadata_get_all (which is a get by origin actually) to origin_metadata_get_by.

This could either take an origin_id and a provider_type (defaulting to None) or a dict of filters.
And depending on the parameters, would call inside the db module the right sql function?

You'd also need to unify the information returned (that is join on the provider table to return those information even in the case of the get_by_origin, to return more than just the provider id).

same :)