[
https://issues.apache.org/jira/browse/KNOX-3026?focusedWorklogId=911909&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-911909
]
ASF GitHub Bot logged work on KNOX-3026:
----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Mar/24 20:00
Start Date: 27/Mar/24 20:00
Worklog Time Spent: 10m
Work Description: smolnar82 opened a new pull request, #893:
URL: https://github.com/apache/knox/pull/893
## What changes were proposed in this pull request?
//TODO: this is still under eating, I just wanted to have this out for
review ASAP.
## How was this patch tested?
I added and updated existing JUnit tests.
E2E testing on a real CM cluster is ongoing...
Issue Time Tracking
-------------------
Worklog Id: (was: 911909)
Remaining Estimate: 0h
Time Spent: 10m
> Exclude services/roles from being discovered
> --------------------------------------------
>
> Key: KNOX-3026
> URL: https://issues.apache.org/jira/browse/KNOX-3026
> Project: Apache Knox
> Issue Type: Improvement
> Affects Versions: 2.0.0, 1.6.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Critical
> Fix For: 2.1.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, even after implementing KNOX-2899, CM service discovery is running
> on the entire CM cluster and fetches information on all services and roles
> that are available on that target cluster. We may want to revisit the
> service-based discovery enablement (that is now disabled by KNOX-2899).
> However, there is a need for end-users to be able to declare services and
> roles that should be explicitly excluded during service discovery.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
