Skip to content

Commit 13962c8

Browse files
committed
fix: config conversion failing due to missing enabled property
1 parent 3b31b82 commit 13962c8

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

.github/utils/yml_config_validation.sh

+2-2
Original file line numberDiff line numberDiff line change
@@ -17,5 +17,5 @@ yq 'true' $input_file /dev/null || exit 1
1717
echo "- checking if ors.engine.source_file exists and has 'source_file' property"
1818
yq --exit-status '.ors.engine | has("source_file")' $input_file > /dev/null || exit 1
1919
# For profiles section for car with enabled using yq and contains
20-
echo "- checking if ors.engine.profiles.car exists and has 'enabled' property"
21-
yq --exit-status '.ors.engine.profiles.car | has("enabled")' $input_file > /dev/null || exit 1
20+
#echo "- checking if ors.engine.profiles.car exists and has 'enabled' property"
21+
#yq --exit-status '.ors.engine.profiles.car | has("enabled")' $input_file > /dev/null || exit 1

docs/run-instance/configuration/ors/engine/profiles.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ These standard profiles are:
2020
| `public-transport` | `public-transport` |
2121

2222
::: warning
23-
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`.
23+
The predefined settings override settings specified in the `profile_default` in your ors-config.yml or ors-config.env!
2424
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`.
2525
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.
2626
:::

0 commit comments

Comments
 (0)