Comment 4 for bug 1891096

All of those commands:

config get <who> {<key>} Show configuration option(s) for an entity
config reset <int> Revert configuration to previous state
config rm <who> <name> Clear a configuration option for one or more
config set <who> <name> <value> Set a configuration option for one or more

and the `assimilate-conf` command (regardless of where it is executed) will update the mon DB.

* `ceph config assimilate-conf -i <input file> -o <output file>`
  will injest a configuration file from *input file* and move any
  valid options into the monitors' configuration database. Any
  settings that are unrecognized, invalid, or cannot be controlled by
  the monitor will be returned in an abbreviated config file stored in
  *output file*. This command is useful for transitioning from legacy
  configuration files to centralized monitor-based configuration.

So, there is no code path that would do something like this:

ceph.conf -> osd -> mon config database

rather

ceph.conf -> client -> mon config db