#2945 RFE: Provide a solution so local override data can persist during cache clears
Closed: cloned-to-github by pbrezina. Opened by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1301606

Description of problem:
Currently the SSSD local overrides feature stores its data in the cache,
'/var/lib/sss/db/cache_*'.
It's not uncommon to clear the cache for various reasons, it'd be nice have a
more permanent location for this data so it can persist when the cache is
cleared.
Maybe have a location, in /var/lib/sss or /etc/sssd/ that will contain an
export. Then apart of the start process or the process of creating the cache,
that an import is performed if an export exists.
Version-Release number of selected component (if applicable):
N/A
How reproducible:
N/A
Steps to Reproduce:
1.
2.
3.
Actual results:
N/A
Expected results:
N/A
Additional info:

This is more or less an investigation task. We've been asked by the field to research this, but it's not urgent to warrant 1.14 alpha, beta should be fine.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
milestone: NEEDS_TRIAGE => SSSD 1.14 beta
review: True => 0
selected: =>
testsupdated: => 0

Should not block the 1.14 beta release.

milestone: SSSD 1.14 beta => SSSD 1.14 backlog

Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.

milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: bugzilla

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3986

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

Metadata