Observed behavior
When a sync fails on startup no error is thrown, and remaining syncs hang
Expected Behavior
Error log indicating that the file config/samples/I-dont-exist.json does not exist
Steps to reproduce
start flagd with the following command:
./flagd start --uri file:config/samples/example_flags.json --uri file:config/samples/I-dont-exist.json --debug
output:
1.6752602188585558e+09 debug runtime/from_config.go:76 using filepath sync-provider for: "file:config/samples/example_flags.json" {"component": "runtime"}
1.675260218858582e+09 debug runtime/from_config.go:76 using filepath sync-provider for: "file:config/samples/I-dont-exist.json" {"component": "runtime"}
1.6752602188586729e+09 info file/filepath_sync.go:29 Starting filepath sync notifier {"component": "sync", "sync": "filepath"}
1.67526021885871e+09 info file/filepath_sync.go:29 Starting filepath sync notifier {"component": "sync", "sync": "filepath"}
1.6752602188590488e+09 info service/connect_service.go:108 metrics listening at 8014 {"component": "service"}
with the console hanging
No response
Observed behavior
When a sync fails on startup no error is thrown, and remaining syncs hang
Expected Behavior
Error log indicating that the file
config/samples/I-dont-exist.jsondoes not existSteps to reproduce
start flagd with the following command:
output:
with the console hanging
No response