Unidata
Convert runtime files into YAML
As to the registry.xml the new ldmadmin (Python) already parses it seamlessly. Should it be included in the conversion?
What's crucial is whether or not a programmatic library exists for parsing the particular configuration-file. One exists for XML, so "registry.xml" could be left alone. Parsers for the other configuration-files, however, are hand-coded.
Indeed, I had once a syntactic error in the ldmd.conf file that the current yy parser could not point me to. Will do for the all .conf files, acknowledging however the impact on their current usage in both the new ldmadmin and the underlying C code (pqact, etc.), as well as their backward incompatibility.
Oh, and on the user... (the mandatory learning curve and the subsequent ease of use and robustness thereafter)
This issue is very low priority because 1) the amount of effort is significant; 2) user's are used to the current solution; 3) providing forward and rollback compatibility is very non-trivial (the configuration-files would have to be automatically converted to the new format and changes to the new configuration-files would have to be rolled back into the old configuration-files); and 4) there are, doubtless, more important issues.
So, don't work on it if you were planning too.
This issue was more aspirational (i.e., wishful thinking) on my part.
On Tue, Apr 6, 2021 at 10:59 AM mustbei @.***> wrote:
Indeed, I had once a syntactic error in the ldmd.conf file that the current yy parser could not point me to. Will do for the all .conf files, acknowledging however the impact on their current usage in both the new ldmadmin and the underlying C code (pqact, etc.), as well as their backward incompatibility.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Unidata/LDM/issues/68#issuecomment-814279102, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEVZ7PHKE27RYYWC2LGHEDTHM4YLANCNFSM4GWKUNZA .