There are couple issues here. We need to differentiate the initial construction and editing the INI file. The INI reader currently ignores the comments and skips broken entries reporting them as errors. If we want to be able to create and edit the INI files we would have to deal with preserving comments, empty spaces and in some way dealing with broken lines. This is not a trivial problem. Augeas really more suitable for editing the INI file because it can easily deal with these issues. We can add functionality to create a new initial INI file pretty easily but is it worth it? It can be done via augeas too. Let us think more about it before we jump and start doing something here. I am not aginst doing it but let us think more before we decide what to do.

There are couple issues here. We need to differentiate the initial construction and editing the INI file. The INI reader currently ignores the comments and skips broken entries reporting them as errors. If we want to be able to create and edit the INI files we would have to deal with preserving comments, empty spaces and in some way dealing with broken lines. This is not a trivial problem. Augeas really more suitable for editing the INI file because it can easily deal with these issues. We can add functionality to create a new initial INI file pretty easily but is it worth it? It can be done via augeas too. Let us think more about it before we jump and start doing something here. I am not aginst doing it but let us think more before we decide what to do.

There are couple issues here. We need to differentiate the initial construction and editing the INI file. The INI reader currently ignores the comments and skips broken entries reporting them as errors. If we want to be able to create and edit the INI files we would have to deal with preserving comments, empty spaces and in some way dealing with broken lines. This is not a trivial problem. Augeas really more suitable for editing the INI file because it can easily deal with these issues. We can add functionality to create a new initial INI file pretty easily but is it worth it? It can be done via augeas too. Let us think more about it before we jump and start doing something here. I am not aginst doing it but let us think more before we decide what to do.

Fields changed

component: SSSD => INI Parser
milestone: Iteration 5 => Deferred
status: new => assigned

Fields changed

component: SSSD => INI Parser
milestone: Iteration 5 => Deferred
status: new => assigned

Fields changed

component: SSSD => INI Parser
milestone: Iteration 5 => Deferred
status: new => assigned

There is not real driver for this functionality.

doc: => 0
docupdated: => 0
proposed: => 2.0
tests: => 0
testsupdated: => 0

There is not real driver for this functionality.

doc: => 0
docupdated: => 0
proposed: => 2.0
tests: => 0
testsupdated: => 0

There is not real driver for this functionality.

doc: => 0
docupdated: => 0
proposed: => 2.0
tests: => 0
testsupdated: => 0

Fields changed

milestone: SSSD Deferred => Tools 1.0

Fields changed

milestone: SSSD Deferred => Tools 1.0

Fields changed

milestone: SSSD Deferred => Tools 1.0

The new INI code is easily capable of this. Moving to value objects instead of the string values helped a lot.

The new INI code is easily capable of this. Moving to value objects instead of the string values helped a lot.

The new INI code is easily capable of this. Moving to value objects instead of the string values helped a lot.

Fields changed

rhbz: => 0

Fields changed

rhbz: => 0

Fields changed

rhbz: => 0

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
milestone: Tools Backlog => Tools 2.0
patch: => 0

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
milestone: Tools Backlog => Tools 2.0
patch: => 0

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
milestone: Tools Backlog => Tools 2.0
patch: => 0

Ticket is moved out of sssd issue tracker.

https://pagure.io/SSSD/ding-libs/issue/56

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

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.