CLI plugins with HTTP protocol option not being recognized

[JillieBeanSim]

in Zowe CLI v 6.30.0 plugins could have their own protocol option for connection to be HTTP, any version above that starting with 6.31.0 to the present 6.37.7 when a user sets the protocol for the plugin to HTTP the following error is returned

not sure what changed between 6.30.0 and 6.31.0 for this error to occur.

[github-actions]

Thank you for creating a bug report. If you haven't already, please ensure you have provided steps to reproduce it and as much context as possible.

[zFernand0]

Hey @JillieBeanSim,
After trying unsuccessfully to reproduce the issue, we believe it might be best to get together in order to find a suitable solution.

[ItsKipz]

Hello,

I am experiencing this same issue, but it is happening on every connection regardless of whether i set it to HTTP or HTTPS.

This is happening across two different computers (one Mac, one Windows), and is also happening using Zowe Explorer for VSCode.

The server is not the issue, I can connect to it using other software.

[phaumer]

@zFernand0 would be better to get rid of the protocol option in Zowe profiles altogether? I think this could be done for v3.

[zFernand0]

zFernand0 would be better to get rid of the protocol option in Zowe profiles altogether? I think this could be done for v3.

We could consider something like this.
Question for you though,
Would you expect to pass a <protocol>://<hostname or ip> combination on instead of just the host?

@adam-wolfe may help us determine whether we can still include this in the V3 plan 😋

[phaumer]

@zFernand0 no, I would stick with the host and port properties and only remove protocol. Therefore, default Zowe CLI would only support https for z/OSMF. Other plugins can add other properties for whatever they want to support, e.g. ftp might bring protocol back for its own profiles to distinguish sftp from ftps.