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

Refactor: Merge Config and ProfileInfo APIs #2396

Open
t1m0thyj opened this issue Dec 23, 2024 · 1 comment
Open

Refactor: Merge Config and ProfileInfo APIs #2396

t1m0thyj opened this issue Dec 23, 2024 · 1 comment
Labels
enhancement New feature or request new The issue wasn't triaged yet v4 Prospective changes for v4

Comments

@t1m0thyj
Copy link
Member

t1m0thyj commented Dec 23, 2024

Is your feature or enhancement request related to a problem or limitation? Please describe

As a Zowe extender, it is difficult to know which profile API is best to use and inconvenient when I need to use both.
As a Zowe core maintainer, there is duplication across the profile APIs which requires extra maintenance.

Describe your enhancement idea

Merge the Config and ProfileInfo APIs into a single API that can be used both by Zowe CLI and extenders to manage team config.

Describe alternatives you've considered

Extenders can currently use both APIs by calling ProfileInfo.getTeamConfig to access the Config API.

Provide any additional context

Perhaps the profiles features of Imperative could be split out into a separate SDK - see #1969

It might be useful to pull in some of the profile methods from Zowe Explorer to consolidate even more APIs.

@t1m0thyj t1m0thyj added enhancement New feature or request new The issue wasn't triaged yet labels Dec 23, 2024
@github-project-automation github-project-automation bot moved this to New Issues in Zowe CLI Squad Dec 23, 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 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

@t1m0thyj t1m0thyj added the v4 Prospective changes for v4 label Dec 23, 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 new The issue wasn't triaged yet v4 Prospective changes for v4
Projects
Status: New Issues
Development

No branches or pull requests

1 participant