-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Some properties are only present in che.properties #14946
Comments
everest properties are consumed there no ? https://github.com/codenvy/everrest |
@benoitf Yes, the everrest properties are used -- this is just the output of a script to review. I think some properties are left over from the Che 6 workspaces deprecation. I'm not familiar with all of them, however. |
@amisevsk that is just a small list of unused property right? For instance we still have a lot of |
@l0rd The list is just a list of the properties whose only mention in the Che server codebase is in Edit: Added as review on #14951: #14951 (review) |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
/remove-lifecycle stale |
Is your task related to a problem? Please describe.
While working on #14633 I came across a number of properties that are only mentioned in
che.properties
and used nowhere in the code (that I can see):che.websocket.endpoint_minor
che.workspace.maven_server_java_options
che.workspace.terminal_linux_amd64
che.workspace.terminal_linux_arm7
che.workspace.exec_linux_amd64
che.installer.registry.remote
che.template.storage
che.docker.enable_container_stop_detector
notification.server.propagate_events
org.everrest.asynchronous.pool.size
org.everrest.asynchronous.queue.size
org.everrest.asynchronous.job.timeout
org.everrest.asynchronous.cache.size
org.everrest.asynchronous.service.path
che.singleport.wildcard_domain.port
che.singleport.wildcard_domain.ipless
If these properties are actually unused in Che 7, they should be removed.
The text was updated successfully, but these errors were encountered: