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

vNext: ZE is unable to create standard `base` profile #2887

Closed zFernand0 closed 1 week ago

zFernand0 commented 2 months ago

Describe the bug

When you first load Zowe Explorer, and try to create your very first team config file, there is no base profile created as a result. image

To Reproduce

  1. Get a clean environment (no ~/.zowe directory)
  2. Install the latest vNext version (v3.0.0-next.202404242037)
  3. Create a new team config file

    To have a base profile created

    Desktop (please complete the following information):

    • OS: Windows (Sandbox)
    • Zowe Explorer Version: vNext
    • (Optional) Zowe CLI Version: N/A
    • (Optional) Are you using Secure Credential Store? N/A

    Additional context

    See below 😋

    I'm seeing some strange behavior with packaging and installing both extensions. When I created a new team config no base or ftp profile was put in the config. Also, when I first started I did the create steps to add ftp profile to existing config and it wasn't added. When I deleted that config to test starting fresh I saw strange behavior in tree where it didn't clear the profiles (this part could be unrelated but still a problem that should be documented).

    Screenshot 2024-04-02 at 1 43 53 PM

    after deleting config:

    Screenshot 2024-04-02 at 1 43 04 PM

    Originally posted by @JillieBeanSim in https://github.com/zowe/zowe-explorer-vscode/pull/2783#pullrequestreview-1974528094

github-actions[bot] commented 2 months 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 2 months ago

TL;DR: There may be more Imperative configuration needed after the move from CLI to SDKs (#2730)

For additional context, this seems to have always been the case for the purposes of ConfigBuilder (even before the imperative migration).

So, something seems to have regressed in the way we do our version of config init between the following pre-release versions:

Here is a quick Diff in case you are interested: