Uncaught Exception during config rewrite

Sorry, I must decline this patch. If a module tries to replace any "not existing" configuration, it must inform the user and immediately abort the module installation. Because the replacement of not existing configuration would definitely lead to errors.

No worries: I do understand what you are trying to do Artem.

I am proposing you two alternatives:
1., Use an install hook for this and use the optional folder to install config in dependence of existing config.
2., I won't allow the config replace module to install modules and log errors which you will ignore. As an alternative you could implement a property which will be optionally set during the module install. This property would be propagated to config replace, so that it would install only config if the original config is existing and log useful info logs, which would not be scary. Like "Bypassing config xyz, because original config is not existing". The current behavior helps a lot in preventing wrong config.

One more thing: If you extend the config replace module, you "must" provide an automated test. Unit tests or kernel base tests are welcome. It seems that you do not like to write tests, but still: it is a must.

3. Behaviour with patch: the module will be installed, the changes to admin/content view will be applied, the changes to admin/media will be skipped and logged to watchdog with a proper exception handling.

You wrote that you want to skip config. Therefor you could set an option for this in your install hook. Also you could implement a method call for installing your config, if you foresee a "skipping".

I do not want to pollute my logs with errors which will be ignored.

Testing exception handling is a basic method in unit testing.

If this module is useless for you: do not use it.

It is not a must to always catch exceptions. An exception is good for showing "why" something is failing. Therefor the NonexistentInitialConfigException is being implemented.

I don't really see any reason why this module replaced the config_rewrite module that was doing absolutely the same.

The project description describes the reason:

Replaces existing configuration on module installation via using a "rewrite" folder in the config directory. Stops with an error, if you are going to replace a config without having the original config in your database (a difference to the Configuration Rewrite module).

There has been lots of broken configs in deGov because configs from the "rewrite" folder where propagated into the database, without having the original config. Configuration replace does NOT install any modules that want to replace not existing original configuration.

Something like this could be implemented in your module install hook (second parameter is new):

\Drupal::service('config_replace.config_replacer')->rewriteModuleConfig($module, TRUE);

That would skip the replacement of configuration, without having original configuration.

A more granular config management by separating config into modules or using the optional config folder could also solve the issue.

I have proposed you a date for a google hangout session to talk about this. It's up to you to attend.

1. I agree with patch provided here by @artem. At least it gracefully will log the error instead of breaking the website.
2. Due to config translations we need to provide an option so creating configuration files that do not exist yet works. As all configuration in deGov should be in English and it should also provide the German translation configuration files. See patch.
3. I am also not sure why it was chosen here to create a complete copy of the module config_rewrite instead of using a patch on that module? Was some attempt done to reach the maintainer or to ask for co-maintenance of the module?

Scratch the above patch of mine. I was confused for a while, because I was too focused with the rewrite folder. Of course in case new configuration needs to be written it would be in the config/install folder.