[IntelMQ-dev] IEP01: IntelMQ Configuration Handling

[Bernhard Reiter]

Hi Sebastian,

Am Donnerstag 14 Januar 2021 16:51:37 schrieb Sebastian Wagner:
> Either these proposals are overwhelmingly

to me they were overwhelmingly big, so I did not fully think them through. 

> YAML-libraries for Python also support comments which can be
> /preserved/, even when the file is edited by other means (intelmqctl as
> well as IntelMQ Manager).

But preserving comments without them being part of the structured data to be 
shown and edited by a tool (like the manager) means they are potentially 
wrong, or "broken", once the tool edits the parameters.
This will make all tools be second citizens. Most of my mails were
about explaining this, no consensus necessary here as it follows by the nature 
of the data by arguments.

A potential solution to this is to make comments part of the structured data
(no matter what format is chosen).

Consensus could be build about if it is okay to live with the negative 
consequences of second class tools (that may break comment and value 
consistency when used). Or about if the drawbacks of a overcomplicated format
are worth a faster typing in most situations. :)

For both questions I don't know enough about the user base of IntelMQ
to have an informed opinion. (As a person doing service  on the code I'd 
implement what users would like most.)

Best Regards,
Bernhard


-- 
www.intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.cert.at/pipermail/intelmq-dev/attachments/20210114/f3cd11ea/attachment.sig>