Bug 457910
Summary: | memberOf: Make the filter of the treated entries configurable | ||
---|---|---|---|
Product: | [Retired] 389 | Reporter: | Andrey Ivanov <andrey.ivanov> |
Component: | Server - memberOf Plug-in | Assignee: | Nathan Kinder <nkinder> |
Status: | CLOSED WONTFIX | QA Contact: | Chandrasekar Kannan <ckannan> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 1.1.2 | CC: | benl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-12 21:08:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 434915 |
Description
Andrey Ivanov
2008-08-05 11:18:44 UTC
The hardcoded filter is simply a default filter for the memberOf fix-up task. The task filter can be specified in the task entry that is created as the "filter" attribute, which is the recommended thing to do when creating the fix-up task. The fixup-memberof.pl utility that creates the fixup task entry has a "-f" option for specifying this filter. We could add another configuration setting that allows you to configure the default task filter if one is not specified in the task, but I don't see a lot of value in doing so. I also do not want to make this configuration setting required, so we would still need a hardcoded default. If it's only the default filter for the memberOf fix-up task, you are right. There is no need to create another configuration parameter. I thought (or maybe it was the case in one of the previous code versions) that there was a limitation on the "real time" updates of the entries. After looking through the latest version of the code the filter is indeed used exclusively in the fix-up task. Thanks for your input, Andrey. Since you agree with my assessment, I'm going to close this bug. |