af9dfb0dba
Change-Id: I02f3adf9825636e2b81c50543d6f95ea986019b6 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
33 lines
930 B
Bash
33 lines
930 B
Bash
#!/bin/bash
|
|
|
|
if [[ ! -d "/var/log/kolla/valkey" ]]; then
|
|
mkdir -p /var/log/kolla/valkey
|
|
fi
|
|
|
|
if [[ $(stat -c %a /var/log/kolla/valkey) != "755" ]]; then
|
|
chmod 755 /var/log/kolla/valkey
|
|
fi
|
|
|
|
# The CONFIG REWRITE command rewrites the valkey.conf
|
|
# file the server was started with, applying the minimal
|
|
# changes needed to make it reflect the configuration
|
|
# currently used by the server, which may be different
|
|
# compared to the original one because of the use of
|
|
# the CONFIG SET command.
|
|
#
|
|
# https://valkey.io/commands/config-rewrite/
|
|
#
|
|
# Because of above behaviour it's needed to
|
|
# hack kolla's CMD.
|
|
#
|
|
# Without this hack
|
|
# /usr/local/bin/kolla_set_configs --check
|
|
# is always reporting changed.
|
|
#
|
|
# Therefore valkey-sentinel is always restarted
|
|
# even if configuration is not changed from
|
|
# kolla-ansible side.
|
|
if [ ! -z "${VALKEY_CONF}" ] && [ ! -z ${VALKEY_GEN_CONF} ]; then
|
|
cp ${VALKEY_CONF} ${VALKEY_GEN_CONF}
|
|
fi
|