You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (Jira)" <ji...@apache.org> on 2020/09/23 20:13:00 UTC
[jira] [Resolved] (SLING-9764) Support regex pattern matching of
the content for the server.ready.path checks
[ https://issues.apache.org/jira/browse/SLING-9764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Norman resolved SLING-9764.
--------------------------------
Resolution: Fixed
Fixed at: https://github.com/apache/sling-org-apache-sling-testing-serversetup/commit/209d5633e88bed18b25737132934b04a3a7c6a72
> Support regex pattern matching of the content for the server.ready.path checks
> ------------------------------------------------------------------------------
>
> Key: SLING-9764
> URL: https://issues.apache.org/jira/browse/SLING-9764
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: Apache Sling Server Setup Tools 1.0.2
>
>
> Check for a third segment in the property value and if the value is "regexp" then use the get#checkContentRegexp api instead of the get#checkContentContains api to check if the content contains the value.
> For example if you want to use the heath check path to determine if all required services are available but you don't want to hard code the number of required services, you could use something like this to check for the expected pattern:
>
> {code:java}
> <server.ready.path.1>/system/health?tags=systemalive&format=json:All \d+ required services are available:regexp</server.ready.path.1>{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)