DAL/Node: improve profile handling
The following discussion from !13137 (merged) should be addressed:
-
@Saroupille started a discussion: (+3 comments) We should consider modifying the current UX so that there is only one source of truth for the profile while currently they are two:
- configuration file
- profile file
Also:
In case of a restart, the profile file takes indeed precedence over the config file and the CLI. But that's only relevant in case of a change between the three profile types: random observer, bootstrap, and operator. In case of such a change, I'd say it would be better UX-wise to fail with a warning about a profile incompatibility between the newly specified profile (in the config or in the CLI) and the profile from the previous run (in the
profiles.json
file).