[
https://issues.apache.org/jira/browse/KNOX-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975359#comment-16975359
]
Kevin Risden commented on KNOX-1654:
------------------------------------
bq. But, testing this is a major issue, there is no way we can safely test all
the services that rely on them (we don't know which ones rely on global rules
or which global rule service).
But the same argument you can't test this jira ticket either then. Just adding
another config makes it that much harder to test.
bq. This ticket is to handle the edge cases, this is not meant to be a feature
but to prevent edge cases that were encountered in the field.
What edge cases? The description has no such edge case defined. There needs to
be some concrete example of where this matters. Right now all this global
avoidance logic is hidden in individual service definitions as work arounds
(basically redefine the same rewrite rule and ends up overridding the global
rule). What would be removed from service definitions if this change is made?
> Ability to exclude global rewrite rules
> ----------------------------------------
>
> Key: KNOX-1654
> URL: https://issues.apache.org/jira/browse/KNOX-1654
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Sandeep More
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently we have some services whose rewrite rules are global, the
> configuration is in gateway-site.xml. We need to be able to add a list of
> services that can be excluded so that global rules do not affect them.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
