Configuration workflow variable simplification with reuse of input PFX

[pavelzlatnik]

Customer content

In configuration workflow for zowe and for API ML, there are setup variables which could be simplified.

There is requested PFX for zowe MVS datasets.
It could be re-used, and 4 variables could be constructed within the workflow, and stored into yaml file, so there is no need to request it from user.
(JCL LIbrary, utilities library, plugin library, apf auth library)

Describe the solution you'd like
Remove those 4 variables from "UI" input, and rather construct them dynamically from input prefix and hardcoded suffix

Describe alternatives you've considered

Additional context

---

Engineering team info (eg https://github.com/zowe/explorer-jes/issues/4)

As a sysprog,
I want simplify need/requested input variables
so that zowe/ API ML configuration via configuration workflow is more streamlined.

Details/notes
[Detail - implementation notes]

Acceptance Criteria

*Scenario 1: [Title]
Given [context]
And [some more context]...
When [event]
Then [outcome]
 And [another outcome]...

[pavelzlatnik]

Discussed with "zowe config team" and with "API ML team", and conclusion is to keep those defaults visible and enable to user have them fully independent and not hide&tied them together, so I am closing this simplification idea.