Description
When load_config_file is called from bootstrap scripts (containerized CLI wrappers), the log messages print container paths instead of host paths, which can confuse users.
Context
The bootstrap scripts now resolve host paths before passing them to load_config_file, but the function logs one of the arguments directly. This creates misleading output for users when the scripts run inside containers.
The native scripts also use load_config_file, so a flag could be introduced to determine whether the method is called in a bootstrap script or a native script to control the logging behaviour.
References
Follow-up
This will be addressed in a future PR when cleaning up the bootstrap/native scripts.
Description
When
load_config_fileis called from bootstrap scripts (containerized CLI wrappers), the log messages print container paths instead of host paths, which can confuse users.Context
The bootstrap scripts now resolve host paths before passing them to
load_config_file, but the function logs one of the arguments directly. This creates misleading output for users when the scripts run inside containers.The native scripts also use
load_config_file, so a flag could be introduced to determine whether the method is called in a bootstrap script or a native script to control the logging behaviour.References
sbinvia Docker Compose; Remove redundant assets from the package (resolves #1358). #1512sbinvia Docker Compose; Remove redundant assets from the package (resolves #1358). #1512 (comment)Follow-up
This will be addressed in a future PR when cleaning up the bootstrap/native scripts.