Add option to zowe config init to allow users to create a nested config

[adam-wolfe]

Is your feature or enhancement request related to a problem or limitation? Please describe

zowe config init creates a non-nested/flat config with one profile of every type available in the schema. This works fine for users who only need to connect to one system, however, users accessing multiple systems will need to make structural modifications to the team config to nest profiles by LPAR/sysplex.

Describe your enhancement idea

Give users the option to generate a nested config with zowe config init. We could allow users to specify the number of nested profiles to create, or we could just make one nested profile (with no base profile) and let them copy that structure in the json to get however many nested profiles they might need. It would be simpler to assign default profiles using the latter option.

Describe alternatives you've considered

An alternative could be to implement an interactive team config creation wizard that prompts the user for things like:

• Number of systems
• Then for each system, prompt for:
  • Host address
  • Access method (APIML vs. direct-to-service)
    • I think this would be mostly safe, however it could be possible for base paths to differ depending on how a given system is configured.
  • Authentication method (basic auth vs. client cert)
  • Service profile properties (?)
    • Note: This may not be feasible, since there could be any number of installed plug-ins/profile types with a huge number of available properties. It may be better to only build the nesting structure and let users manually modify the profile properties in the JSON.
• Default system (populate the defaults using services from a given system)

Provide any additional context

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

[ATorrise]

Currently working on this for innovation week. Depending on progress, I will make a PR based on my functional changes for the next branch https://github.com/ATorrise/zowe-gui/blob/wip/README.md

Currently I have a gui window pop up that is triggered by running zowe config init

As of 7/31 I am working on creating a config file with either 1, 2 or 3 levels of nesting from information gathered by this GUI