Draupnir should scream if it is started without the explicit --draupnir-config argument, because the legacy modes of starting Draupnir without config are fragile.

[Gnuxie]

If we haven't already deprecated using the environment variables to select a config, we should now.

We should also verify that Draupnir refuses to start if the path specified with --draupnir-config cannot be found.

Related: #217

[FSG-Cat]

Because spantaleev/matrix-docker-ansible-deploy#3128 is merged this change can be made without affecting playbook users that are up to date as of whenever a change like this is made in a negative way.

[Gnuxie]

So to improve the situation we have included

Tue, 08 Oct 2024 11:28:13 GMT [WARN] [Draupnir config] DEPRECATED Starting Draupnir without the --draupnir-config option is deprecated. Please provide Draupnir's configuration explicitly with --draupnir-config. config path used: /home/user/experiments/Draupnir/config/harness.yaml

At startup via #604. Whether this is enough yet we'll figure out

[Gnuxie]

To be honest we should make this log message bigger, probably by putting the Please provide... part on its own line.