Bug #21598
Updated by Sebastian Wagner about 4 years ago
This is kind of confusing for users and for module developers.
Originally the config-key stuff was meant to just be a backend, and the user interface was meant to be for the plugins to just expose their own CLIs for setting options safely (including validation etc). We've sort of diverged from that now -- we will soon (hopefully) be moving to a central KV store for all config keys, so for the moment we should either just document this or find some intermediate solution (like maybe adding a mgr command that sets config options in a way that does update the cached copies in the mgr).
Workaround is something like
<pre>
ceph config-key set mgr/my_module/my_setting value
ceph mgr restart
</pre>