The new philosophy around the new errata process is that oval data information is only generated upon errata release (all pkgs are matched, added and published updaterecord/packages in pulp repos, marked as "released" in database, etc). Then, when requesting for oval xml, we just need to take generated data to compile the final document. But what happens with already released records?
We have unused fields in our data model, checked production database and:
all oval-related criteria, tests, states, objects and variables from new_errata_records are null
reboot suggested is always "false" - we have 2 options, keep it as is or dump all the handling around AND hardcorde where needed
For this reason, we are creating a migration script that adds all oval data for all released erratas in those empty fields, because right now with the current implementation, this is calculated every time we call get_oval_xml. This way, we don't need to calculate every time, just take all oval data from records and compile the final oval document.
This covers the following requirements:
Support the new errata workflow
Ensure that, just in case where we need to go back to the previous workflow, the data is preserved and we can keep generating errata as before
The new philosophy around the new errata process is that oval data information is only generated upon errata release (all pkgs are matched, added and published updaterecord/packages in pulp repos, marked as "released" in database, etc). Then, when requesting for oval xml, we just need to take generated data to compile the final document. But what happens with already released records?
We have unused fields in our data model, checked production database and:
For this reason, we are creating a migration script that adds all oval data for all released erratas in those empty fields, because right now with the current implementation, this is calculated every time we call get_oval_xml. This way, we don't need to calculate every time, just take all oval data from records and compile the final oval document.
This covers the following requirements: