action #163229
opencoordination #152769: [epic] Reduction of yaml files in YaST installations
Reduce yaml files for activate_encrypted_volume+{force_recompute,import_users} for powerVM
0%
Description
Motivation¶
See epic and tickets in the epic for best practices.
It is a follow-up of #153562 to cover also powerVM.
Some general summary as a hint (after reading previous tickets):
Main goals are to reduce for single test suite to single yaml file comparing the ones created per each architecture before and drive the schedule having different yaml default files per each architecture. The final yaml should be stored in a folder where we have the representation of each test case: schedule/yam/test_cases
In order to do that you have to consider if it is just about yaml or would require some code changes to make things more homogeneous, there are multiple approaches ranging from simple dropping small tested functionality in some specific architecture to some more fancy code strategy.
At the same time we should care of variables, basically moving all of them to job group yaml.
Leave out for now ppc64le, due to most of our test coverage is in PowerVM and it is not working, so verification are not possible atm. Anyway in the future most likely we will have to reduce hugely test coverage for ppc64le, so we should take that into account instead of trying to do much effort in the code due to PowerVM requires special treatment in the console or installation that only make sense to have them in textmode breaking this homogeneity that we are aiming to.
Specific from this test suite:
Schedules for this test suite exists in schedule/yast/encryption.
Acceptance criteria¶
AC1: Reduce yaml files for corresponding test suite over all the architectures and apply those extra clean-up when corresponding.
AC2: Clean-up unused files.
No data to display