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

Team conf file creation will add global_base if base already included in config #3141

Open
JillieBeanSim opened this issue Sep 23, 2024 · 1 comment
Labels
bug Something isn't working priority-medium Not functioning - next quarter if capacity permits Research Needed severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex. v3
Milestone

Comments

@JillieBeanSim
Copy link
Contributor

Describe the bug

Team conf file creation will add global_base if base already included in config. This seems it could become problematic.
ZE would merge existing config details into a new if user confirmed the overwriting of existing file, we may want to add a check for existing base and either not include the global_base or project base named profiles or change name of existing base profile to recommended for v3.

To Reproduce

Steps to reproduce the behavior:

  1. have an existing v2 team config
  2. Click on + and create new team config where existing is located
  3. See both base profile names existing in team config.

Expected behavior

Screenshots

Desktop (please complete the following information):

  • OS:
  • Zowe Explorer Version:
  • (Optional) Zowe CLI Version:
  • (Optional) Are you using Secure Credential Store?

Additional context

@JillieBeanSim JillieBeanSim added bug Something isn't working v3 labels Sep 23, 2024
Copy link

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

@JTonda JTonda added priority-medium Not functioning - next quarter if capacity permits severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex. labels Sep 24, 2024
@zowe-robot zowe-robot moved this from New Issues to Medium Priority in Zowe Explorer for VS Code Sep 24, 2024
@t1m0thyj t1m0thyj assigned traeok and unassigned traeok Oct 2, 2024
@JillieBeanSim JillieBeanSim added this to the v3.0.2 milestone Oct 14, 2024
@JillieBeanSim JillieBeanSim modified the milestones: v3.0.2, v3.0.3 Oct 17, 2024
@JillieBeanSim JillieBeanSim modified the milestones: v3.0.3, v3.1.0 Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-medium Not functioning - next quarter if capacity permits Research Needed severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex. v3
Projects
Status: Medium Priority
Development

No branches or pull requests

3 participants