As a developer I want be able to not maintain duplicated code in relation to distro_signatures.jsonso that I can take advantage of the advanced functionality of this library in the main server.
Some remarks for this issue:
If there are changes required to this library to make access for consumers of the library easier, let's discuss it and do it, we haven't tagged anything yet
The CLI of this library needs to be mature enough to work with existing distro_signatures.json files
The serialization for the server items we need to adjust since that is at the moment storing the strings for the versions. If we switch to the DAO (data access objects) here, then we need to be careful with serialization and the XML-RPC API.
My idea for the timeline is the following:
This project is being integrated into the main server codebase in a pre-release (let's say something alike 0.1.0)
We test everything before a Cobbler release
We iterate the first two points before this one until we are happy with the results
As a developer
I want be able to not maintain duplicated code in relation to
distro_signatures.jsonso that I can take advantage of the advanced functionality of this library in the main server.Some remarks for this issue:
distro_signatures.jsonfilesMy idea for the timeline is the following:
Code usages I was able to identify:
Additionally the CLI has some usages but we ignore those as we will not put effort into a deprecated CLI. The effort needs to be put into the Golang CLI. This CLI can be progressed as soon as https://github.com/cobbler/cobbler/issues/3164 (with PR https://github.com/cobbler/cobbler/pull/3244) is fixed (merged) and we have merged https://github.com/cobbler/cobblerclient/pull/10 on the CLI.