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

V3: Migrate away from @zowe/cli to @zowe/*-for-zowe-sdk packages #2719

Closed
Tracked by #3005
zFernand0 opened this issue Feb 14, 2024 · 1 comment · Fixed by #2730
Closed
Tracked by #3005

V3: Migrate away from @zowe/cli to @zowe/*-for-zowe-sdk packages #2719

zFernand0 opened this issue Feb 14, 2024 · 1 comment · Fixed by #2730
Assignees
Labels
enhancement New feature or request priority-high Production outage - this quarter or at least next quarter v3
Milestone

Comments

@zFernand0
Copy link
Member

Is your feature request related to a problem? Please describe.

We should leverage the full capabilities of the Node.js SDK without importing functionality directly from the CLI package. In addition to that, the @zowe/cli package comes with an npm-shrinkwrap.json file which makes sense for the CLI. However, this may indicate that we have to wait for the CLI to release a new update before Zowe Explorer can fix any transitive dependencies.

Describe the solution you'd like

Instead of @zowe/cli, to import:

  • @zowe/zos-files-for-zowe-sdk for data set and USS operations
  • @zowe/core-for-zowe-sdk for any configuration related matters across Zowe Explorer
  • @zowe/zos-tso-for-zowe-sdk for TSO related operations
  • ...and others

Describe alternatives you've considered

To continue with the CLI dependency, which has the an npm-shrinkwrap. This can force us to use yarn.resolutions or pnpm.overrides if we have to update some transitive dependency, but this can have negative effects (luckily none so far)

Additional context

This was discussed during the extended ZE standup on Feb 13th, 2024

Copy link

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

@zFernand0 zFernand0 added this to the v3.0.0 GA milestone Feb 14, 2024
@JTonda JTonda added priority-high Production outage - this quarter or at least next quarter v3 labels Feb 15, 2024
@zowe-robot zowe-robot moved this from New Issues to High Priority in Zowe Explorer for VS Code Feb 15, 2024
@t1m0thyj t1m0thyj self-assigned this Feb 20, 2024
@t1m0thyj t1m0thyj linked a pull request Mar 5, 2024 that will close this issue
16 tasks
@t1m0thyj t1m0thyj closed this as completed Mar 5, 2024
@github-project-automation github-project-automation bot moved this from High Priority to Closed in Zowe Explorer for VS Code Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-high Production outage - this quarter or at least next quarter v3
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants