You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm interested in having the /search endpoint return the constraints (Kibana requirements) and owner (maintaining Github team). This would be useful information to have when filtering on the search results.
For example with elastic-package status, which uses /search to collect information on the status of packages in the registry, this data could be included in the output (or used to filter). It might be used to determine what packages are exclusively available in 7.N, but are not in production.
The fields would need moved to BasePackage (or a separate SearchResponse type could be created).
This adds the constraints.kibana.version and owner fields to /search responses.
It also removes HTML escaping from the JSON responses to make them more readable.
Closeselastic#731
This adds the constraints.kibana.version and owner fields to /search responses.
It also removes HTML escaping from the JSON responses to make them more readable.
Closes#731
I'm interested in having the
/search
endpoint return theconstraints
(Kibana requirements) andowner
(maintaining Github team). This would be useful information to have when filtering on the search results.For example with
elastic-package status
, which uses/search
to collect information on the status of packages in the registry, this data could be included in the output (or used to filter). It might be used to determine what packages are exclusively available in 7.N, but are not inproduction
.The fields would need moved to
BasePackage
(or a separateSearchResponse
type could be created).package-registry/util/package.go
Lines 73 to 74 in 89b3dd2
The text was updated successfully, but these errors were encountered: