Feature #156

Configure CSV and LDIF output rom the lsc.properties file

Added by Rémy-Christophe Schermesser 8 months ago. Updated 2 months ago.

Status:New Start:29/11/2009
Priority:Normal Due date:
Assigned to:Rémy-Christophe Schermesser % Done:

80%
Category:Core
Target version:1.3.0

Description

It should be nice to be able to configure the CSV and LDIF output from the lsc.properties file and not from the logback.xml file.

What do you think of :

lsc.myTask.CSV = true
lsc.myTask.CSV.logOperations = create, delete
lsc.myTask.CSV.attrs = cn;dn
lsc.myTask.CSV.separator = ; (optional)

For the ldif :

lsc.myTask.LDIF = true
lsc.myTask.LDIF.logOperation = create, delete

Associated revisions

Revision 773
Added by Rémy-Christophe Schermesser 2 months ago

Configure LDIF and CSV output from the lsc.properties files
References #156

History

Updated by Jonathan Clarke 8 months ago

Looks nice, a lot nicer than the logback configuration ;-)

Two comments:
  1. Can we add the filename to write to, as well?
  2. Also, I think it would be clearer if the properties contained the word "log" or "output", to make it clear what we're configuring here.

Apart from that, great :)

Updated by Rémy-Christophe Schermesser 7 months ago

Ok here the v2. I have added the prefix .output., added the filename property and remove the boolean on the root (CSV = true, LDIF = true). It was stupid to add this.

lsc.myTask.output.CSV.filename = /tmp/csv.log
lsc.myTask.output.CSV.operations = create, delete
lsc.myTask.output.CSV.attrs = cn;dn
lsc.myTask.output.CSV.separator = ; (optional)

For the ldif :

lsc.myTask.output.LDIF.filename = /tmp/csv.log
lsc.myTask.output.LDIF.operations = create, delete

Updated by Jonathan Clarke 7 months ago

Rémy-Christophe Schermesser wrote:

Ok here the v2.

Looks good. I will test soon.

Can you pass an option to append / not append to the file? Appending is good for log files to see a history of events, but not appending is good for keeping an up-to-date file containing a list of entries that need changing (for example, if the update condition is false).

Updated by Rémy-Christophe Schermesser 7 months ago

  • Target version changed from 1.2.0 to 1.3.x branch

Retargetting to 1.3, after a new configuration system is made

Updated by Rémy-Christophe Schermesser 2 months ago

  • Target version changed from 1.3.x branch to 1.3.0
  • % Done changed from 0 to 80

The commit r773 has the feature. The documentation is here : http://lsc-project.org/wiki/documentation/1.3/upgrade-from-1.2.

So now please test it :)

Also available in: Atom PDF