Multiple ini files inside module #310
Comments
bocekm
changed the title
|
Per #281 (comment), this issue will be mitigated by PR #311 by that preupg-content-creator will not generate 2 INIs. However the thing that the Preupgrade Assistant crashes because preupg-xccdf-compose generates gibberish when it encounters multiple INIs, will still persist. |
|
I still don't understand why multiple INIs should affect the The reason of this behaviour is the most probably instide the The variable |
Previously building of module set has been corrupted when directory with the module contained more than one file with the ".ini" extentions. Build of the module set shouldn't be affected by various INI files, that are not related to the module set structure. So the scan is now read only group.ini and module.ini files whose names are reserved for PA purposes. In addition we expect only one of those files in each directory, so the ModuleSetFormatError exception is raised when both are detected in the same directory. Resolves #310
Previously building of module set has been corrupted when directory with the module contained more than one file with the ".ini" extentions. Build of the module set shouldn't be affected by various INI files, that are not related to the module set structure. So the scan is now read only group.ini and module.ini files whose names are reserved for PA purposes. In addition we expect only one of those files in each directory, so the ModuleSetFormatError exception is raised when both are detected in the same directory. - removed unused import of ModuleSetUtils Resolves #310
Use settings.module_ini and settings.group_ini in tests. Related #310
When PA generates
group.xmlfile for each module it ussualy collects data only frommodule.ini. Problem is when in module are multiple ini files, then it generates wrong xml (with multiple roots elements).Error looks like:
From:
preupgrade-assistant/preupg/xmlgen/oscap_group_xml.py
Line 77 in 7290804
The text was updated successfully, but these errors were encountered: