The goal of this phase is to convert the existing ROSA wizard to use Formik and Patternfly wizard components. Users should not see any changes compared to today (V1) after this phase is complete. Rosa V2 will have separate screens from OSD v2. For example, Cluster -> Machine Pool screen may exist in OSD v2, and another copy in Rosa v2 -we are not striving to share components as this leads to complex ‘isRosa’ logic, plus later Phases change the order of rosa steps, which we do not want impacting OSD wizard.
Â
Step 1 - Copy current ROSA wizard. This new copy will be known as ROSA V2Â
- Within the rosa_v1 directory, change import paths to components within it to relative paths to make it easier to duplicate the entire directory
- Duplicate the rosa_v1 directory to rosa_v2
- IMPORTANT: Any code changes in the rosa_v1 directory should be also repeated for the rosa_v2 directory until we can switch over to v2 and retire v1
- Add new router entry for the rosa_v2 CreateROSAWizard
- Add ability to switch between rosa_v1 and rosa_v2 wizards (feature gate / URL param?)
Step 2 - Convert ROSA V2 to use Formik:
- Add Formik to rosa_v2 and update review step to work with it
- Convert wizard steps to formik (will be completed by multiple people)
- Components will be copied so it is separate from OSD/ROSA_V1 wizard
Step 3 - Convert ROSA V2 to use the newer PatternFly wizard (and not deprecated)Â
Step 4 - Verify ROSA V2 with QE
Step 5 - Switch feature gate so all traffic is through ROSA V2 wizard
Step 6 - Remove old ROSA V1 code and feature gateÂ
Â
Out of scope:Â Â
- Convert to Typscript
- Convert to Functional Component
- blocks
-
OCMUI-480 Reorganize ROSA HCP wizard to enable quick cluster creation
- To Do
-
OCMUI-1369 Create HCP only version of the ROSA wizard
- To Do
-
OCMUI-1370 Remove ROSA Classic wizard
- To Do
-
OCMUI-1684 Data Sovereignty for ROSA HCP Wizard
- Closed
- causes
-
OCMUI-1712 [ROSA V2 Wizard]Cluster wizard blocked proceeding to next step from Cluster roles and polices step when cluster-wide proxy definition in place.
- Closed
-
OCMUI-1708 [ROSA V2 wizard]"Edit step" actions from "Review and create" step didn't work.
- Closed
-
OCMUI-1710 [ROSA V2 Wizard]Disable the left navigation tree links from wizard not to allow user bypass the steps.
- Closed
-
OCMUI-1713 [ROSA V2 wizard]User allowed to proceed to next steps with selection of "Hosted" control plane card although no quota is available.
- Closed
-
OCMUI-1709 [ROSA V2 wizard]"Back to networking configuration" link from cluster-wide proxy step didn't work.
- Closed
-
OCMUI-1714 [ROSA v2 wizard] Previously selected machine pool definition are not cleared once user change the VPC definition.
- Closed
-
OCMUI-1720 ROSA v2 - Navigation disappears when selecting a cluster-wide proxy
- Closed
-
OCMUI-1723 [ROSA V2 'classic' wizard]Missing validation when same availability zone selected Virtual Private Cloud (VPC) subnet settings
- Closed
-
OCMUI-1728 [ROSA v2 wizard] PrivateLink definition shown as "Disabled" from "Review and create" step of a ROSA HCP private cluster
- Closed
-
OCMUI-1727 [ROSA Wizard v2] "Review and create" page wrongly indicated the "Custom KMS key ARN" although user selection was "Use default KMS Keys".
- Closed
-
OCMUI-1743 [ROSA v2 wizard] Wrong tooltip text definition associated to "Maximum nodes per machinepool" in Hypershift wizard flow.
- Closed
-
OCMUI-1771 [ROSA v2 wizard] "Account role" creation command shown different under "How to associate AWS.. " drawer from ROSA v1
- Closed
-
OCMUI-1772 [ROSA v2 wizard] Do not show "Leave cluster creation" when user navigate from first control plane step to getstarted page.
- Closed
- clones
-
OCMUI-299 OSD Wizard v2
- Closed
- is depended on by
-
OCMUI-1368 [Rosa Wizard] CIDR validation errors do not persist in UI when editing new field
- Closed
-
OCMUI-1669 [ROSA Hypershift] Public subnet definition didn't retained when user navigate from "Review and create" page using "Edit step" option.
- Closed
- is related to
-
OCMUI-1862 [ROSA wizard v2] Compute node type value not validated as required field when user select unsupported compute node type and later changes its definition.
- Closed
- mentioned on