multi-admin workflows integrated for init & config

[1000TurquoisePogs]

The existing workflow seems to take you as far as it can go with 1 user alone, and that's fine to keep as an option, but many can't do that.
As it already notes, different admins are involved in the installation process.
ZEN won't be production-ready until it can handle division of responsibility that real organizations have.

I can't think of a better way to solve this requirement than to embrace zOSMF workflows.
We don't need to reinvent anything there, we could just put zOSMF in an iframe within electron.
We should review the existing zosmf workflows in zowe to see if they are adequate for the experience we want.

I envision:

• certain steps of the install are known to require privilege, and have an associated workflow to do the action required.
• ZEN only needs to know that the action is done, but does not need to be involved in doing the action or reading its output
• on a step like this, the user has the choice to dispatch a workflow, or let ZEN do the job itself, with the user's permission
• if a workflow is dispatched, zosmf in an iframe can be viewed to see the status: the user has to wait until completed.

i think the user could dispatch some workflows in parallel rather than waiting for each admin to do their task before another begins. so, maybe there could be a page of admin actions, with a checkbox selecting whether those pages will be automated or not, in advance.
And, perhaps the zosmf iframe isnt a 'step' in the wizard, but a side action that can be viewed at any step as needed.

since waiting for admins could take time, recording the state is important because the ZEN user may want to close the program and come back another day and resume.

[DivergentEuropeans]

"we could just put zOSMF in an iframe within electron." possible cross-origin issues here? Not sure, don't know enough about Electron

[jp669844]

The existing z/OSMF workflow basically fills the yaml file from z/OSMF UI. Also, I don't think it is possible to put the z/osmf workflow app/screens into an iframe and show it somewhere else. There would be also an issue with SSO, it would need to implement JWT or similar technology. I would suggest to rather implement this: #68.