commit 764dec8d4e36c2aadc3c5d67c8ac2c744e850533
author Edwin Kempin <ekempin@google.com> Wed Sep 22 10:45:01 2021 +0200
committer Edwin Kempin <ekempin@google.com> Wed Sep 22 11:03:06 2021 +0200
tree 08e5092f0f98bd4f961ef739a56d5516cb44fb2e
parent 4bc8c946351a6e5fa7adc6217a0fcc9448ae364f

RequestConfig: Allow to specify excluded request URI patterns

RequestConfig is used to

* enable tracing by configuration
* set a server side deadline

for matching requests.

Requests can be matched by project, request type, request URI pattern
and calling user.

Using request URI pattern it is easy to match requests for certain
REST endpoints, e.g. to match requests for the submit REST endpoints
it's possible to set 'requestUriPattern = /changes/.*/submit'. However
it was difficult to match all REST endpoint except certain REST
endpoints, like matching all REST endpoints except the submit REST
endpoints. To support this better we add a new parameter to
RequestConfig that allow admins to define request URI patterns that
should be excluded. This way  matching all REST endpoints except the
submit REST endpoints can be expressed by 'requestUriPattern = .*' (or
leaving it unset since matching all requests is the default value) and
`excludedRequestUriPattern = /changes/.*/submit'.

If a request URI is matched by excludedRequestUriPattern the
RequestConfig is not matching even if the request URI matches
requestUriPattern. Or vice versa, if a request URI is matched by
requestUriPattern the RequestConfig is not matching if the request URI
also matches excludedRequestUriPattern.

Same as for requestUriPattern it is possible to specify
excludedRequestUriPattern multiple times.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I907a08617219805cf2f5a5a4fea9bfcd24b5bb36