Skip to content

Refactor: Merge Config and ProfileInfo APIs #2396

Open
@t1m0thyj

Description

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestpriority-lowLegit issue but cosmetic or nice-to-havev4Prospective changes for v4

    Type

    No type

    Projects

    • Status

      Low Priority

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions