coordination #71242: [epic] Unify validation in the installed system
Unify test data for guided partitioning
Recently it was created this structure for handling guided partitioning with REST API:
test_data: guided_partitioning: filesystem_options: root_filesystem_type: ext4
Later on we realized it would not be efficient to have a different data structure for each module we create as far as we could use a common shared structure. For expert partitioning we already have that structure:
disks: - name: vda table_type: gpt allowed_unpartitioned: 0.00GB partitions: - name: vda2 formatting_options: filesystem: ext4 mounting_options: should_mount: 1 mount_point: /
As we can see, we are repeating the information, in this example filesystem 'ext4'.
AC1: Rewrite guided_setup.pm so we can iterate over common structure and extract mount point and filesystem.
AC2: Run verification wherever the module is used (TW x86_64, TW aarch, Leap, SLES, maintenance updates).
#8 Updated by JERiveraMoya over 1 year ago
- Tags changed from qa-yast-to-refine, qe-YaST-to-refine, YaST to refine, qe-yast-refinement, refinement-qe-yast to qa-yast-to-refine, qe-YaST-to-refine, YaST to refine, qe-yast-refinement, refinement-qe-yast, to_refine_qe_yast, to refine qe yast, To Refine QE YaST