Migration info printed even if using yaml

[joewragg]

Is there an existing issue for this?

• I have searched the existing issues

Problem description

It seems that the migration info is printed each time I start the application even though I can see it is picking up my yaml config

Proposed solution

Make it false by default

Additional context

No response

Forum Topic Link

No response

[joewragg]

#################
--
# Container ENV #
#################
�[32m✓ CONTAINER_LOG_LEVEL: INFO. Set CONTAINER_LOG_LEVEL=DEBUG for more details.�[0m
�[34mⓘ Any config file settings can be overwritten by environment variables.�[0m
�[34mⓘ Use 'CONTAINER_LOG_LEVEL=DEBUG' to see the full list of active environment variables for this container.�[0m
###########################
# Container sanity checks #
###########################
�[34mⓘ Running container as user ors with id 1000 and group 1000�[0m
�[32m✓ ORS_HOME: /home/ors exists and is writable.�[0m
�[32m✓ Update the file /home/ors/config/example-ors-config.env with /example-ors-config.env�[0m
�[32m✓ Update the file /home/ors/config/example-ors-config.yml with /example-ors-config.yml�[0m
�[32m✓ Using the existing ors-config.yml from: /home/ors/config/ors-config.yml�[0m
�[34mⓘ Default to graphs folder: /home/ors/graphs�[0m
�[34mⓘ Any ENV variables will have precedence over configuration variables from config files.�[0m
�[32m✓ All checks passed. For details set CONTAINER_LOG_LEVEL=DEBUG.�[0m
#####################################
# Container file system preparation #
#####################################
chown: /home/ors/graphs: Operation not permitted
chown: /home/ors/graphs: Operation not permitted
chown: /home/ors/files: Operation not permitted
chown: /home/ors/files: Operation not permitted
chown: /home/ors/logs: Operation not permitted
chown: /home/ors/logs: Operation not permitted
chown: /home/ors/elevation_cache: Operation not permitted
chown: /home/ors/elevation_cache: Operation not permitted
�[32m✓ Update the file /home/ors/files/example-heidelberg.osm.gz with /heidelberg.osm.gz�[0m
�[32m✓ Container file system preparation complete. For details set CONTAINER_LOG_LEVEL=DEBUG.�[0m
#######################################
# Prepare CATALINA_OPTS and JAVA_OPTS #
#######################################
�[32m✓ CATALINA_OPTS and JAVA_OPTS ready. For details set CONTAINER_LOG_LEVEL=DEBUG.�[0m
�[34mⓘ ##########################################�[0m
�[34mⓘ # Config options and migration information #�[0m
�[34mⓘ ##########################################�[0m
�[34mⓘ >>> Migration information <<<�[0m
�[33m⚠ Configuring ors with a .json config is deprecated and will be removed in the future.�[0m
�[34mⓘ You can use the ors-config-migration tool to migrate your .json config to .yml: https://github.com/GIScience/ors-config-migration#usage�[0m
�[34mⓘ >>> Config options <<<�[0m
�[34mⓘ You have the following options to configure ORS:�[0m
�[34mⓘ Method 1 yml config:�[0m
�[34mⓘ > docker cp ors-container-name:/home/ors/config/example-ors-config.yml ./ors-config.yml�[0m
�[34mⓘ > docker run --name example-ors-instance-conf-file -e ORS_CONFIG_LOCATION=/home/ors/config/ors-config.yml -v $(pwd)/ors-config.yml:/home/ors/config/ors-config.yml openrouteservice/openrouteservice:latest�[0m
�[34mⓘ Method 2 environment variables:�[0m
�[34mⓘ > docker cp ors-container-name:/home/ors/config/example-ors-config.env ./ors-config.env�[0m
�[34mⓘ > docker run --name example-ors-instance-env-file --env-file ors-config.env openrouteservice/openrouteservice:latest�[0m
�[34mⓘ >>> End of migration information <<<�[0m
`