Overriding *_CONFIG configurations #22640
godwinjoel
started this conversation in
General
Replies: 1 comment 1 reply
-
In your environment, you can setup something like this so you can have it in single directory:
We didn't expect users to be modifying the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@ldziedziul, @frant-hartm, @obedsoto
Concerns distribution/src/bin-filemode-755/hz file.
As a user, when I override my config directory using HAZELCAST_CONFIG,
I expected the following -
LOGGING_CONFIG="file:$HAZELCAST_CONFIG/log4j2.properties"
PROMETHEUS="-javaagent:${HAZELCAST_HOME}/lib/jmx_prometheus_javaagent-0.17.2.jar=${PROMETHEUS_PORT}:${HAZELCAST_CONFIG}/jmx_agent_config.yaml"
But it seems all these other configurations still look for relevant files in $HAZELCAST_HOME/config instead of $HAZELCAST_CONFIG
Is this by design? With the current setup, I need to manage different configuration files in at least two other folders.
Beta Was this translation helpful? Give feedback.
All reactions