Kea issueshttps://gitlab.isc.org/isc-projects/kea/-/issues2023-04-13T13:47:19Zhttps://gitlab.isc.org/isc-projects/kea/-/issues/2818Read YAML configuration file2023-04-13T13:47:19ZVicky Riskvicky@isc.orgRead YAML configuration fileIn today's webinar on configuring custom options, a participant asked whether we could enable configuration in YAML instead of JSON. Carsten revealed that he uses a YAML <-> JSON translator so he can work in YAML but still feed Kea JSON....In today's webinar on configuring custom options, a participant asked whether we could enable configuration in YAML instead of JSON. Carsten revealed that he uses a YAML <-> JSON translator so he can work in YAML but still feed Kea JSON. It was suggested that maybe we could make Kea recognize whether the configuration file is in YAML or JSON, and in case of YAML, run this translator first. It seems like there might be a useful usability improvement in here somewhere.backloghttps://gitlab.isc.org/isc-projects/kea/-/issues/290Arguments/parameters for hooks and commands are not checked2023-02-25T19:27:17ZFrancis DupontArguments/parameters for hooks and commands are not checkedChild of #229 for all hooks.Child of #229 for all hooks.backloghttps://gitlab.isc.org/isc-projects/kea/-/issues/1996Add Gitlab pipeline buttons that regenerate messages and parsers2022-11-02T15:10:40ZAndrei Pavelandrei@isc.orgAdd Gitlab pipeline buttons that regenerate messages and parsersThe buttons would be similar to the deploy buttons in stork.
I want this mainly for parsers because people regenerate with different bison versions. And Kea sometimes reaches a state where different bison versions are used for different...The buttons would be similar to the deploy buttons in stork.
I want this mainly for parsers because people regenerate with different bison versions. And Kea sometimes reaches a state where different bison versions are used for different parser files. And I don't know if it's safe to test Kea like that throughout the development process. And maybe people feel more comfortable clicking a button in Gitlab which adds a commit that regenerates the parsers for them with the bison version that was settled to be used than to keep upgrading the bison on their machine.
But we could add one for messages as well so that we don't have to --enable-generate-messages all the time.backloghttps://gitlab.isc.org/isc-projects/kea/-/issues/1507recode decommentJSONfile to handle tricky cases2021-03-18T15:53:05ZFrancis Dupontrecode decommentJSONfile to handle tricky casesAs we now have /* */ comments in example files the simple decommentJSONfile() tool should be improved.
According to its doxygen comment:
```
/// Removes //, # and /* */ comments from the input file and writes its content
/// to another f...As we now have /* */ comments in example files the simple decommentJSONfile() tool should be improved.
According to its doxygen comment:
```
/// Removes //, # and /* */ comments from the input file and writes its content
/// to another file. The comments are replaced with spaces, so the original
/// token locations should remain unaffected. This is rather naive
/// implementation, but it's probably sufficient for testing. It won't be able
/// to pick any trickier cases, like # or // appearing in strings, nested C++
/// comments etc at the exception of // in URLs.
```
Note it is not required now and not trivial so I create it in Outstanding.outstanding