fix: config conversion failing due to missing enabled property

GIScience · Apr 19, 2024 · 13962c8 · 13962c8
1 parent 3b31b82
commit 13962c8
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/.github/utils/yml_config_validation.sh b/.github/utils/yml_config_validation.sh
@@ -17,5 +17,5 @@ yq 'true' $input_file /dev/null || exit 1
 echo "- checking if ors.engine.source_file exists and has 'source_file' property"
 yq  --exit-status '.ors.engine | has("source_file")' $input_file > /dev/null || exit 1
 # For profiles section for car with enabled using yq and contains
-echo "- checking if ors.engine.profiles.car exists and has 'enabled' property"
-yq  --exit-status '.ors.engine.profiles.car | has("enabled")' $input_file > /dev/null || exit 1
+#echo "- checking if ors.engine.profiles.car exists and has 'enabled' property"
+#yq  --exit-status '.ors.engine.profiles.car | has("enabled")' $input_file > /dev/null || exit 1
diff --git a/docs/run-instance/configuration/ors/engine/profiles.md b/docs/run-instance/configuration/ors/engine/profiles.md
@@ -20,7 +20,7 @@ These standard profiles are:
 | `public-transport`             | `public-transport`                           | 
 
 ::: warning
-The predefined settings override settings specified in the `profile_default` in your ors-config.yml or ors-config.env! This also means that you cannot enable all default profiles by simply setting `profile_default.enabled` to `true`.  
+The predefined settings override settings specified in the `profile_default` in your ors-config.yml or ors-config.env!  
 If you want to specify your own profile settings based on your specific `profile_default` values, you can work around this by naming your profile differently, e.g. `custom-car` instead of `car`. 
 Note that the profile name can be chosen freely but cannot contain special characters that cannot be used for directory names on your operating system. 
 :::