search

zowe / zowe-explorer-vscode

Visual Studio Code Extension for Zowe, which lets users interact with z/OS Data Sets, Unix System Services, and Jobs on a remote mainframe instance. Powered by Zowe SDKs.
Eclipse Public License 2.0
159 stars 89 forks source link

Nested configuration file issues seen by extenders #2982

Open JillieBeanSim opened 3 days ago

JillieBeanSim commented 3 days ago

Describe the bug

using a parent profile as opposed to a base profile. This is a problem implementing this in my VSCode Explorer extension . I provide the means to allow the user to set his credentials in my Explorer extension as an alternative to forcing the user to have zowe cli installed . I have it working fine with various combinations of profile but not when using an untyped parent profile with typed profiles beneath. if I put SecureArgs in that parent as per your article, there is no way as far as I can see of retrieving that untyped parent profile using ProfInfo as it is not typed and there is no easy way of knowing that a child profile is in fact a child . zowe cli does all this without any issues but not so the VSCode Extensionwhwre it is proving to be a nightmare . Any suggestions as to what I seem to be missing here? Thanks David !!

cont.

could do what the zowe config secure —gc does by using profInfo.getTeamConfig().api.secure.secureFields() It returns the full pathname of the arg which is fine but it still leaves the problem of identifying what the argument type is and then how to update it back to the vault. So the arg could be ‘user’ but we need to know if it is a string etc and putting it back to the vault isn’t easy as profInfo.updateProperty requires a profile type and again the root profile is untyped ! It seems way more complicated than it needs to be in my humble opinion.. even more so for us trying to get this to work in the VSCode Extension world

may be related to https://github.com/zowe/zowe-explorer-vscode/issues/2264

We cannot assume how the team configuration file is laid out with the schema supporting so many different ways of configurations. Not sure if this should be solved at our API level or the imperative's IProfileInfo level and should be discussed across squads to determine the best solution for all CLI and VSC ZE extenders for profile management.

To Reproduce

Expected behavior

Screenshots

Desktop (please complete the following information):

Additional context

github-actions[bot] commented 3 days ago

Thank you for creating a bug report. We will investigate the bug and evaluate its impact on the product. If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

zFernand0 commented 3 days ago

This may be related to: