Motivation
We want to use the /meta resource to add non-mds-standard-information to entities, majorly geographies and policies.
E. g. we want to "tag" policies with a type, meaning the policy regulates a fleet.
However, we cannot query for this information easily, but we need to retrieve the full data set and filter afterwards.
Proposal
Add a query parameter to the APIs for reading entities (mds-policy, mds-geography-api) which joins and filters based on metadata. Since meta holds a JSON, this will have to translate to a fancy query on the particular services.
Imho, it's fine to query only for equality (no pattern-patching or other operators).
/policies?meta.type=fleet should be sufficient. Of course, supporting the additional jsonb operators is an option as well, but I don't know if this is consumer friendly ;)
Motivation
We want to use the
/metaresource to add non-mds-standard-information to entities, majorly geographies and policies.E. g. we want to "tag" policies with a type, meaning the policy regulates a fleet.
However, we cannot query for this information easily, but we need to retrieve the full data set and filter afterwards.
Proposal
Add a query parameter to the APIs for reading entities (
mds-policy,mds-geography-api) which joins and filters based on metadata. Sincemetaholds a JSON, this will have to translate to a fancy query on the particularservices.Imho, it's fine to query only for equality (no pattern-patching or other operators).
/policies?meta.type=fleetshould be sufficient. Of course, supporting the additionaljsonboperators is an option as well, but I don't know if this is consumer friendly ;)