Zowe CLI V2 - Independence between profile name and internal organization of the zowe.config[.user].json file

[FALLAI-Denis]

Hi,

With Zowe CLI V2, profile names are dependent on the internal organization of the information stored in the zowe.config[.user].json file.

According to this organization, a profile that ultimately logically represents the same context would have a different name.

This is not acceptable: the name of a profile must remain independent of the internal organization of the zowe.config[.user].json file.

I proposed in issue #1404 another internal organization of the zowe.config[.user].json file which replaces management by hierarchy (which impacts the name of the profile) by management by import (which maintains the name of the profile).

Confer https://github.com/zowe/zowe-cli/issues/1404#issuecomment-1120725726

Another solution can be considered, the important thing is that the name of the profile is not dependent on the internal organization of the zowe.config[.user].json file.

Confer also #1406.

[FALLAI-Denis]

A solution can be to introduce "alias" to address profile.

This can be a new "aliases" array property in zowe.config[.user].json at root of document, and each item is an object with a property porting the alias name and value reference the profile name.

[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.