#1008 Make sssd api conf file location configurable
Closed: Fixed None Opened 9 years ago by myllynen.

Currently SSSDConfig.py has hardcoded references to /etc/sssd/sssd.api.conf and /etc/sssd/sssd.api.d but they are not real configuration files and not intended to be edited.

Please make location of the sssd.api.* files configurable at ./configurable time.


Fields changed

component: SSSD => SSSDConfig API
milestone: NEEDS_TRIAGE => SSSD 1.8.0
owner: somebody => sgallagh

Fields changed

milestone: SSSD 1.8.0 => SSSD 1.9.0

Fields changed

type: defect => enhancement

Fields changed

blockedby: =>
blocking: =>
priority: major => blocker

Fields changed

blocking: => 1158

Fields changed

blockedby: => 1158
blocking: 1158 =>

Fields changed

blockedby: 1158 =>

Fields changed

resolution: => fixed
status: new => closed

Fields changed

resolution: fixed =>
status: closed => reopened

Fields changed

feature_milestone: =>
rhbz: => 0

Fields changed

status: reopened => new

Fields changed

patch: 0 => 1
status: new => assigned

Fields changed

priority: blocker => trivial

I was confused by the "patch set" option being set. We only fixed the first half of the ticket by moving the API files to a better location but we never made them configurable. This still needs fixing.

milestone: SSSD 1.9.0 => SSSD 1.9.1
owner: sgallagh => jhrozek
patch: 1 => 0
status: assigned => new

Fields changed

milestone: SSSD 1.9.1 => SSSD 1.9.2

This was fixed in f1ce53a

resolution: => fixed
status: new => closed

Metadata Update from @myllynen:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.9.2

3 years ago

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/2050

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.

Login to comment on this ticket.

Metadata