Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vnext version 3.0 of Zowe Explorer uses a non-existent API #2918

Closed
gejohnston opened this issue May 16, 2024 · 2 comments · Fixed by #2932
Closed

Vnext version 3.0 of Zowe Explorer uses a non-existent API #2918

gejohnston opened this issue May 16, 2024 · 2 comments · Fixed by #2932
Assignees
Labels
bug Something isn't working priority-high Production outage - this quarter or at least next quarter severity-high Bug for which there may be workaround but limits the usage of the Zowe for major use cases

Comments

@gejohnston
Copy link
Member

Describe the bug

I noticed that in the next branch of ZE, the file zowe-explorer-vscode/packages/zowe-explorer-api/src/profiles
/ProfilesCache.ts uses the function imperative.ConfigBuilder.convert.

The function imperative.ConfigBuilder.convert no longer exists in the next branch of the Zowe CLI SDK. I suspect that the ZE team used an older snapshot of the CLI vNext SDK, and has not yet updated to use a newer snapshot.

I think that once ZE uses a newer CLI SDK version, ZE will not even compile. ZE code will have to be refactored to use a new CLI SDK function and interfaces before ZE will work again.

I open this issue so that the ZE team is aware of failures that will likely occur after they perform a routine update to a newer version of the CLI SDK.

To Reproduce

Expected behavior

Screenshots

Desktop (please complete the following information):

  • OS:
  • Zowe Explorer Version:
  • (Optional) Zowe CLI Version:
  • (Optional) Are you using Secure Credential Store?

Additional context

Copy link

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.

@JTonda JTonda added priority-high Production outage - this quarter or at least next quarter severity-high Bug for which there may be workaround but limits the usage of the Zowe for major use cases labels May 16, 2024
@zowe-robot zowe-robot moved this from New Issues to High Priority in Zowe Explorer for VS Code May 16, 2024
@JTonda
Copy link

JTonda commented May 16, 2024

This will have to be addressed when we update our cli sdks.

@JillieBeanSim JillieBeanSim moved this from High Priority to In Progress in Zowe Explorer for VS Code Jun 4, 2024
@JillieBeanSim JillieBeanSim modified the milestones: v2.18.0, v3 pre-releases Jun 4, 2024
@JillieBeanSim JillieBeanSim linked a pull request Jun 4, 2024 that will close this issue
16 tasks
@JillieBeanSim JillieBeanSim linked a pull request Jun 14, 2024 that will close this issue
16 tasks
@JillieBeanSim JillieBeanSim linked a pull request Jun 14, 2024 that will close this issue
16 tasks
@JTonda JTonda closed this as completed Jul 25, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Closed in Zowe Explorer for VS Code Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-high Production outage - this quarter or at least next quarter severity-high Bug for which there may be workaround but limits the usage of the Zowe for major use cases
Projects
Status: Closed
Development

Successfully merging a pull request may close this issue.

3 participants