[patch] UDS/DRO migration storage class fix

[yuvraj-vansure]

• MASCORE-2054: prompt user for storgaclass during uds to dro migration.
• removed mirror-dro flag from help doc
• Added skip check for UDS/DRO if DRO already exists during migration.

depending Ansible PR
ibm-mas/ansible-devops#1263

[lokesh-sreedhara]

cam someone help review/approve this PR for merge?

[andrercm]

@yuvraj-vansure @lokesh-sreedhara have you tested if this works as expected for both interactive/non-interactive aproaches and also including --no-confirm argument?

[lokesh-sreedhara]

@yuvraj-vansure @lokesh-sreedhara have you tested if this works as expected for both interactive/non-interactive aproaches and also including --no-confirm argument?

@andrercm ohh i did not check --no-confirm. @yuvraj-vansure can u help with this? when mas update --no-confirm is run, it should overide all user prompts, make sure DRO_STORAGE_CLASS takes default value "" on --no-confirm

[andrercm]

This will be approved to be merged due time constraints, but adjustments will be implemented so that code follows same standard as other implementations in the MAS CLI.

I had a review session with Lokesh and Yuvraj and we identified some enhancements to be done:

• Add logic in update pipeline to skip uds task based on UDS_ACTION valid values, instead of adding skip action into ansible-devops role... If a task must be skipped, it should be proactively skipped in the pipeline instead of being skipped in the role execution.
• Fix the logic on how the DRO_STORAGE_CLASS is determined so it follows same standards as the other places where we define the storage classes. Use https://github.com/ibm-mas/cli/blob/master/image/cli/mascli/functions/internal/install_config_storage_classes as example.