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.

Sign up for GitHub

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

Jump to bottom

v3: Remove V1 profile functionality in vNext (retaining the ability to convert from V1 to V2 configs) #1703

Closed
Tracked by #1740
, #1708 ,  #1671 ,  #1726 ,  #1809 ,  #1971
...
adam-wolfe opened this issue Apr 27, 2023 · 2 comments
Closed
Tracked by #1740
, #1708 ,  #1671 ,  #1726 ,  #1809 ,  #1971
...

v3: Remove V1 profile functionality in vNext (retaining the ability to convert from V1 to V2 configs) #1703

adam-wolfe opened this issue Apr 27, 2023 · 2 comments
Assignees
@gejohnston
Labels
enhancement New feature or request priority-high Production outage - this quarter or at least next quarter v3 prospective changes for v3
Milestone
Zowe V3

Comments

@adam-wolfe
Copy link
Contributor

adam-wolfe commented Apr 27, 2023 •
edited
Loading

In the vNext branch, remove support for V1 profiles.

Based on conversations between the CLI and Explorer squads, we should plan to remove most of the V1 profile functionality (i.e., the ability to use v1 profiles to interact with mainframe services).

We should retain the ability to convert a user's profiles from V1 profiles to the V2 team config.
@adam-wolfe adam-wolfe added enhancement New feature or request new The issue wasn't triaged yet v3 prospective changes for v3 and removed new The issue wasn't triaged yet labels Apr 27, 2023
@github-actions
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.

@adam-wolfe adam-wolfe mentioned this issue Apr 27, 2023
Closed
28 tasks
@adam-wolfe adam-wolfe added the priority-high Production outage - this quarter or at least next quarter label May 2, 2023
@adam-wolfe adam-wolfe added this to the Zowe V3 milestone May 2, 2023
This was referenced Jul 3, 2023
Closed
Closed
@adam-wolfe adam-wolfe mentioned this issue Sep 21, 2023
Closed
20 tasks
@adam-wolfe adam-wolfe changed the title v3: Remove V1 profile functionality in vNext v3: Remove V1 profile functionality in vNext (retaining the ability to convert from V1 to V2 configs) Sep 29, 2023
@adam-wolfe adam-wolfe mentioned this issue Nov 20, 2023
Closed
26 tasks
@t1m0thyj t1m0thyj moved this to High Priority in Zowe CLI Squad Dec 26, 2023
@t1m0thyj t1m0thyj moved this from High Priority to PI Backlog in Zowe CLI Squad Dec 26, 2023
@t1m0thyj t1m0thyj moved this from PI Backlog to Release Backlog in Zowe CLI Squad Dec 26, 2023
@t1m0thyj t1m0thyj moved this from Release Backlog to PI Backlog in Zowe CLI Squad Dec 26, 2023
@t1m0thyj t1m0thyj mentioned this issue Jan 22, 2024
Closed
@adam-wolfe adam-wolfe mentioned this issue Feb 26, 2024
Closed
23 tasks
@gejohnston gejohnston mentioned this issue Mar 11, 2024
Merged
4 tasks
@gejohnston gejohnston moved this from PI Backlog to Review/QA in Zowe CLI Squad Mar 13, 2024
@gejohnston
Copy link
Member

Delivered this enhancement in PR #2085

@github-project-automation github-project-automation bot moved this from Review/QA to Closed in Zowe CLI Squad Mar 14, 2024
@jace-roell jace-roell mentioned this issue May 22, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gejohnston gejohnston

Labels
enhancement New feature or request priority-high Production outage - this quarter or at least next quarter v3 prospective changes for v3
Projects
None yet
Milestone
Zowe V3
Development

No branches or pull requests
2 participants
@gejohnston @adam-wolfe