config: Remove confusing magic in path handling
1. When passed a .yaml path (or any path with a non-whitelisted extension), don't read .yml instead when the .yaml exists. It's an extremely surprising behavior. 2. If the .yaml file does not exist, it will still try alternative extensions in order not to break existing deployments which may rely on it, but it raises a warning now. 3. When given a non-existing path, show an error log, but keep parsing it as an empty config, in order not to break existing deployments.
parent
906769ae
No related branches found
Tags v2.22.1
-
mentioned in merge request swh-vault!182 (merged)
-
mentioned in commit anlambert/swh-vault@7ec97e6c
-
mentioned in commit anlambert/swh-fuse@62784609
-
mentioned in merge request swh-fuse!85 (merged)
-
mentioned in commit anlambert/swh-scanner@1967e48f
-
mentioned in merge request swh-scanner!84 (merged)
-
mentioned in commit anlambert/swh-web-client@20371218
-
mentioned in merge request swh-web-client!31 (merged)
Please register or sign in to comment