Eliminate or reduce the dotted path on the command line flags for profile names

[gejohnston]

This issue represents an enhancement request resulting from customer feedback.

With old profiles one would type:

zowe endevor list elements --endevor-profile lpar1
zowe zos-tso issue command "time" --zosmf-profile lpar1

but with team-config one must type:

 zowe endevor list elements --endevor-profile lpar1.endevor
 zowe zos-tso issue command "time" --zosmf-profile lpar1.zosmf

If users stick to the standard names then the “.endevor” and “.zosmf” are redundant, I think that the lpar1. endevor and lpar1.zosmf etc. would be frustrating to use.

Superficial assessment:

• Maybe when profiles are nested, we could find the first profile under the supplied node (like lpar1 in the example above) which matches the specified profile type (like --zosmf-profile).
• Not sure if this approach will cause other usability issues in other scenarios.

[t1m0thyj]

What version of vNext has the customer been testing? Prior to 7.0.0-next.202108121907, the behavior of "config init" was to create a nested template with profiles named lpar1.XXX.

This issue is still valid when nested profiles are in use. However, I wonder whether the customer would have encountered the issue at all, if the nested profiles had not been present in their default config template.

In the latest @next preview, the default profile names would be "endevor" and "zosmf" without any dotted paths.

[gejohnston]

The customer definitely started with an earlier vNext version. I think he later ran "config init" again and either updated an existing config or pasted his old LPAR1 section (which he renamed from LPAR1) into the new config.

I say this because ssh and zftp were not underneath LPAR1.

I tried to explain in an email that nesting under a node like LPAR1 is not necessary. Perhaps my explanation was not clear. None-the-less, I assumed that he eventually wants to specify multiple LPARs and would have at least one level of nesting for each LPAR.

[github-actions[bot]]

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.