[knot-dns-users] conf-import semantics unclear

Hi, I'm seeking some clarity over the semantics of 'knotc conf-import'. I'm using v3.6.1, specifically. When using the +nopurge filter with an existing configuration database, the operation fails without the use of the -f (force) option. I'm unclear on the intended semantics. Does +nopurge merge configuration in the database with settings imported from the file, or does it just skip the import altogether? Why is the force option required? $ knotc -f conf-import /usr/local/etc/knot/knot.conf +nopurge error: use force option to modify/overwrite the existing destination and ensure the server is not running! Thanks, B.C.