Proceed when config path is missing for environment #3630
Conversation
|
For reference, the important lines are here: https://github.com/kanidm/kanidm/blob/master/server/daemon/src/main.rs#L565 If the command line requests a configuration path with opt.config_path, then we check that it must exist. If no path is requested, we fall through and check if the default config path exists first, and only if it does, then we attempt to force it's use. In this situation, there is no config file present, so this will cause the None case and we skip this. |
|
@Firstyear Sorry to respond to a closed/merged PR, but reading this change randomly and looking into the Dockerfile. |
|
True, it would. I'll fix the PR. |
Change summary
When a configuration path is specified then the server will force it to be used, and will error if it can't be found. The container previously manually specified this path on the command line which forced the configuration to need to exist.
Remove the configuration from the docker cli, the default config path test will discover if the file exists or not and will correctly handle the flow when the file is absent and environment only configuration is used.
Fixes #3617
Checklist