📞📱☎️📡🌐 Cloud Native Telecom Initiative (CNTI) Test Catalog is a tool to check for and provide feedback on the use of K8s + cloud native best practices in networking applications and platforms
The changes to config format proposed in #2121 would make the pre-existing configs of users obsolete, forcing the users to rewrite them. To avoid this hassle a transformer will be implemented that will transform the old format to the newer one.
Possible solution:
Parse/read the file with YAML module -> Change the fields appropriately and create a new YAML structure -> Structure gets stored in class proposed by #2121 (Not part of this issue).
We had a short discussion and it would likely be possible to generate new configs which would resolve the 3rd step of #2120.
As of now the structure of the new config file has not been confirmed (draft in #2129).
kosstennbl
commented
1 month ago
2nd step of #2120.
The changes to config format proposed in #2121 would make the pre-existing configs of users obsolete, forcing the users to rewrite them. To avoid this hassle a transformer will be implemented that will transform the old format to the newer one.
Possible solution: Parse/read the file with YAML module -> Change the fields appropriately and create a new YAML structure -> Structure gets stored in class proposed by #2121 (Not part of this issue).
We had a short discussion and it would likely be possible to generate new configs which would resolve the 3rd step of #2120.
As of now the structure of the new config file has not been confirmed (draft in #2129).