-
Notifications
You must be signed in to change notification settings - Fork 64
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
fix: heap configuration from zowe.yaml #3087
Conversation
Signed-off-by: achmelo <[email protected]>
# Conflicts: # api-catalog-ui/frontend/config-overrides.js
Signed-off-by: achmelo <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
Signed-off-by: achmelo <[email protected]>
Do we want to have the same heap size for all components? Wouldn't be better to have it component-specific? |
It is per component, e.g. ZWE_configs_heap_max is components.gateway.heap.max in zowe.yaml for gateway, if you want to read this value in discovery you would need ZWE_components_gateway_heap_max |
Thank you for explanation |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information The version of Java (11.0.20) you have used to run this analysis is deprecated and we will stop accepting it soon. Please update to at least Java 17. |
Description
Allow users to configure JVM heap parameters from standard zowe.yaml configuration file.
Linked to #2559
Part of the # (epic)
Type of change
Please delete options that are not relevant.
Checklist:
For more details about how should the code look like read the Contributing guideline