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.
Per CS/DS Meeting of 10/12/2015 - 10.3 (confirmed with vakwetu)
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1303158
Per CS Bug/Ticket Triage held 04/19/2016: 10.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.
Per Offline Triage of 11/30/2016-12/01/2016: FUTURE - critical
Metadata Update from @vakwetu: - Issue assigned to vakwetu - Issue set to the milestone: FUTURE
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None - Issue priority set to: major (was: critical)
Per 10.5.x/10.6 Triage: FUTURE
RHBZ: CLOSED UPSTREAM
Metadata Update from @mharmsen: - Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1303158)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2193
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.