Vscode-extension-for-zowe: Clearly specify prerequisite z/OSMF REST services in the README

[MikeBauerCA]

Similar to how the exact z/OSMF REST services for the Zowe CLI are documented at https://docs.zowe.org/stable/user-guide/systemrequirements-zosmf.html#z-os-requirements, we should identify the specific z/OSMF REST services that are required for the functionality offered by the Zowe Explorer.

[IgorCATech]

Do you think we can just insert a link to that Zowe page? Or should there be an additional Zowe Explorer-specific z/OSMF-related page inside the Readme?

[zFernand0]

I tend to believe that duplication of things is never a good approach.
I'd rather recommend adding a link to that specific section, and if there is something that the Zowe Explorer definitely does not require, then we can mention it after the link?
Maybe because I'm not aware of all the details but I do not see an issue if someone wanted to verify/configure all the z/OS requirements on that list. : )

[zFernand0]

@MikeBauerCA Could you help me find the z/OS MF requirements on the Zowe CLI?
I'm curious if these will just be a subset of those. 🤔

[MikeBauerCA]

@zFernand0 it will be a subset of these: https://docs.zowe.org/stable/user-guide/systemrequirements-zosmf.html#z-osmf-rest-services-for-the-zowe-cli

I believe we require TSO/E address space services, z/OS data set and file REST interface, and z/OS jobs REST interface

[zFernand0]

Hey @IgorCATech,
How hard will it be to add another topic to the Confuguring z/OSMF subject?

[zFernand0]

Or maybe a column on that table?
@MikeBauerCA any thoughts?

[MikeBauerCA]

I think another column on that table makes sense. Perhaps the title could be "Required for Zowe Explorer VS Code Extension" and each entry could be a simple Yes or No.

[IgorCATech]

An extra column (or rather a row) in the table sounds good to me. @zFernand0 Can you please consult me on how to populate the description for the Zowe Explorer VS Code Extension requirement?

[zFernand0]

resolved on #305