Bug 1303158 - add Features feature to ldap
Summary: add Features feature to ldap
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 7.4
Assignee: Ade Lee
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-29 17:55 UTC by Matthew Harmsen
Modified: 2018-04-10 20:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 20:28:22 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Matthew Harmsen 2016-01-29 17:55:54 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/pki/ticket/1634

From review point with ftweedal on original Features feature:

> I think that we should store the config in LDAP so that a change on
> one replica is effected on clones.  Obviously this is a fair bit
> more work I am OK with using CS.cfg initially but we should have
> this discussion.
> 

Agreed that this is something we should discuss.  Part of the reason this is system specific though is that people tend to update one system at a time -- in case something goes wrong.  So you can very easily see a situation where a feature is available on one system but not another.

Still, having it in LDAP would allow doing things like enabling features topology-wide for instance.

Comment 2 Matthew Harmsen 2016-04-21 15:42:47 UTC
Per CS Bug/Ticket Triage held 04/19/2016:  RHEL 7.4

Confirmed with alee and ftweedal:

    I think 10.4/RHEL 7.4 is OK; AFAIK we won't have any features likely
    to be dynamically enabled or disabled during deployment lifecycle.

Comment 5 Matthew Harmsen 2018-04-10 20:28:22 UTC
Per RHEL 7.5.z/7.6/8.0 Triage:

edewata: close RHEL bug, keep upstream ticket in FUTURE


Note You need to log in before you can comment on or make changes to this bug.