I don't agree.

- Partners are perfectly capable of updating a key/value object literal.
- Partners will have check that their config matches the latest keys in the default config when they update version anyway as keys or methods of configuration will likely have changed.
- Copying the config, or amending the config directly is negligible work.
- This type of work is called 'build-time' configuration and should be done at build-time. Once 'built' we should have a config.js that is a merge of default and partner settings that our app can just `require()` otherwise we're doing run-time configuration work for *every* launch of the app that could have been done once. I can't suggest how this should be done, but someone more familiar with the build process probably can.
- The extra request may be negligible, but they all add up, and this is something that **can** be avoided.