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
162 stars 90 forks source link

Remove the Delete Profile option from the profile management menu in V3 #3037

Open adam-wolfe opened 1 month ago

adam-wolfe commented 1 month ago

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

In V3, users will not be using V1 profiles. With a team config, the "Delete Profile" option in the profile management menu is functionally identical to the "Edit Profile" option.

Describe the solution you'd like

Remove the "Delete Profile" option from the profile management menu.

It might also be clearer to change "Edit Profile" to "Edit Configuration File" or "Edit Profiles" or something else that indicates that Zowe Explorer will open the team config in an editor tab.

Describe alternatives you've considered

Additional context

github-actions[bot] commented 1 month ago

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.

t1m0thyj commented 1 month ago

As an alternative, should we consider keeping the Delete Profile option and making it work with team config files?

t1m0thyj commented 1 month ago

Created a quick PoC of how the option could work if we decide to keep it: feat/delete-v2-profiles delete-profiles-v2

adam-wolfe commented 1 month ago

As an alternative, should we consider keeping the Delete Profile option and making it work with team config files?

I think that would be ideal.

JTonda commented 1 month ago

Add a warning to prompt for confirmation before deleting that mentions if the profile is a default and if the profile contains child profiles.

zFernand0 commented 1 month ago

Note: The research needed label was added because we would like to determine if it is worth making a change in the underlying Imperative.ProfileInfo APIs in order to ease the burden on extenders and API users when managing profile.