[
https://issues.apache.org/jira/browse/SLING-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000667#comment-16000667
]
Georg Henzler commented on SLING-6804:
--------------------------------------
[~justinedelson] So 1. from above is exactly what I would like to achieve - a
nice simple interface where you can quickly get different results with minimal
URL manipulation. However 2. (and derived 3.) is valid - I didn't notice while
testing because we never use AND (and it does not make much sense to use it
IMHO, but now it's too late to remove that behaviour completely).
So what about the following middle ground:
* We change the HC executor interface and introduce the additional query
parameter {{names}} (as in your patch)
* The path info of the servlet is evaluated in a way that it treats values of
the comma-separated list as tags (if they do not contain a space) or as name
(if a value contains a space).
This semantic is local to the HC servlet (as only that one has the path info),
it can be well-documented and for the very rare case there is a conflict (in
fact I have not seen a tag with space or a HC name without), people can quickly
switch to using the request parameters {{tags}} and {{names}}.
> Request to allow the health check servlet to directly query a single health
> check by name
> -----------------------------------------------------------------------------------------
>
> Key: SLING-6804
> URL: https://issues.apache.org/jira/browse/SLING-6804
> Project: Sling
> Issue Type: Improvement
> Components: Health Check
> Reporter: Clinton H Goudie-Nice
> Assignee: Justin Edelson
> Priority: Minor
> Attachments: SLING-6804-allow-hc.name-in-hc-urls-simple.patch,
> SLING-6804.diff
>
>
> AMS has a request to be able to access an individual health check by name
> For example:
> http://localhost:4502/system/health/named/Sling%20Get%20Servlet.json
> And have it return the results for only this named health check.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
