#56 INI Parser should allow writing out an ini file
Closed: wontfix 2 years ago by atikhonov. Opened 14 years ago by sgallagh.

It should be possible to construct an INI file using the ini_config API and write it out to a file.

This will make it easy for us to write a UI for configuring the SSSD.


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

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

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

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

Metadata Update from @sgallagh:
- Issue assigned to dpal
- Issue set to the milestone: Tools 2.0

7 years ago

AFAIK, there are no plans currently to utilize such a functionality, thus closing as WONTFIX.

Metadata Update from @atikhonov:
- Custom field component adjusted to None (was: INI Parser)
- Custom field patch reset (from 0)
- Custom field selected adjusted to None
- Custom field testsupdated reset (from 0)
- Custom field type adjusted to None (was: enhancement)
- Custom field version adjusted to None (was: 0.4.1)
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata