Hello.
in Kubernetes I can mount a ConfigMap under /mnt/liferay/files (and subfolders) instead of mounting a volume.
These files are exposed as symbolic links to hidden folders, to manage updates on ConfigMaps.
As a result the automatic copy in configure_liferay.sh, creates links and not regular files in the destination folders, and this fact denies modifications of the files (for example to inject credentials or other env variables), because ConfigMaps are immutable inside the container.
At the moment I execute a script before starting the server with the following code:
cd ${LIFERAY_MOUNT_DIR}/files/
find . -not -path '*/\.*' -type d -exec mkdir -v -p ${LIFERAY_HOME}/{} \;
find . -not -path '*/\.*' -not -type d -exec cp -v -H {} ${LIFERAY_HOME}/{} \;
but it's only a workaround.
Is it possible to better support this situation?
thanks
Lorenzo
Hello.
in Kubernetes I can mount a ConfigMap under /mnt/liferay/files (and subfolders) instead of mounting a volume.
These files are exposed as symbolic links to hidden folders, to manage updates on ConfigMaps.
As a result the automatic copy in configure_liferay.sh, creates links and not regular files in the destination folders, and this fact denies modifications of the files (for example to inject credentials or other env variables), because ConfigMaps are immutable inside the container.
At the moment I execute a script before starting the server with the following code:
but it's only a workaround.
Is it possible to better support this situation?
thanks
Lorenzo