-
Notifications
You must be signed in to change notification settings - Fork 92
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
Allow logs folder to be customized in settings #2186
Labels
enhancement
New feature or request
priority-medium
Not functioning - next quarter if capacity permits
Milestone
Comments
t1m0thyj
added
enhancement
New feature or request
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
Mar 16, 2023
Thank you for raising this issue. |
t1m0thyj
removed
the
severity-medium
Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.
label
Mar 17, 2023
21 tasks
21 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
priority-medium
Not functioning - next quarter if capacity permits
Is your feature request related to a problem? Please describe.
In some environments, the VS Code extension path (typically
~/.vscode/extensions
) may be read-only. Zowe Explorer fails to activate when it is unable to create and write to the logs folder inside the extension path.Describe the solution you'd like
Users should be able to customize the path of the logs folder.
Describe alternatives you've considered
Change the default log folder to somewhere else like
/tmp
. However we don't want to needlessly confuse existing users who are happy with the current default behavior.The text was updated successfully, but these errors were encountered: