[c-nsp] IOS(-XE) 'configure replace' robustness

[Saku Ytti]

Does anyone regularly use this to replace configuration with new full
configuration?

e.g. copy config to startup, configure replace nvram:startup-configuration?

I recall trying it when it originally came, and determined that it was
just breaking everything while going towards the new config, and
assumed this was by design.

I just tried it on IOS-XE 16.4.1, and I couldn't recreate my original
problem, what ever changed in the new config, was only thing affected,
non-changing stuff was not impacted.
So I'm curious, does someone actually do this in production, and rely
on it not breaking non-changing config and has had success.

Thanks!
-- 
  ++ytti