When creating new profile from CLI, z/osmf port is not requested, and if default is not used, zowe cli does not work with new profile

[pavelzlatnik]

As for the port not being prompted, zowe-cli assume the default https port (443) for initial configuration.

It did not ask for port specifically during creation as a separate parameter, but as well it is not written how user should specify that. My first idea was as a part of host name, but it does not work as well.

Describe your enhancement idea

It was hard to figure out what is the problem after fresh new install of zowe-cli. And when I have figure out after half day what problem is, when created new profile, I have no way how to specify port from cli. At the end, cli was useless for my case. When I have helped 3 other people with zowe-cli installation week later, I already told them not to create profile from cli, because it would not work, and rather made it by manually by hand (send via email config json and tweak it by hand)

Describe alternatives you've considered

Users have to do manual modification of config json, and already have to know what to do and where, so from that perspective, zowe-cli is useless for profile creation. I would say very bad user experience for someone who would start with zowe-cli without prior knowledge, in case z/osmf is running on different port than 443.

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.

[zFernand0]

Hey @pavelzlatnik,
I'm sorry to hear that you had issues creating a profile 😢

One option is to use the CLI to modify the port number after creating the config file.
zowe config set profiles.zosmf.properties.port 1443 --gc

---

We've had discussions in regards to assigning a default value of 0 to the port property, which will force the CLI to prompt for the password during initialization.

I'm afraid that changing said value might be considered a breaking change at this point, so we gotta make sure we do this in a backwards compatible way 🙏

👀 @adam-wolfe

[gejohnston]

An additional consideration is that within the very definition of a z/OSMF profile, an industry-standard default port number of 443 is defined for the z/OSMF profile. Thus, even though you do not explicitly set a port number in your zowe.config.json, in an environment variable, or on the command line, the port property still has a default value. Zowe CLI commands do not prompt you for a port number as a missing connection property because technically it is not missing. It has the default value of 443, as we see in your screen snapshot of a connection error.

Because many shops alter their port from the default value of 443, it can lead to the automatic use of the wrong 443 port number. We have avoided changing the behavior for all properties with default values, so that we do not introduce breaking changes.

That is the reason why we discussed the possibility of making the port's default value 0 as mentioned above, but even that could be considered a breaking change.

[pavelzlatnik]

OK, thanks for explanation. Would it be in that case possible to add just Note. When is called config init, to place where is generated message Saved config template to ..... , after would be just newline Note that would say
Note: If your z/osmf is running on different port that 443, you can change it via command zowe config set profiles.zosmf.properties.port 1443 --gc