Still exporting config saved in a features custom module

Hi there! Thanks for trying out this module and apologies for not responding for so long.

If I understand your situation correctly, you have configuration in a custom features module and then you have the same configuration file (albeit with different configuration) in an installation profile. If that is the case it is absolutely expected for the profile to "win" and so effectively for your features module to be ignored at least with respect to those configuration files. Drupal core is not very lenient with this sort of "duplicate" configuration, regardless of Config Overlay. For example, if you have two different modules that provide a node.type.article configuration in their config/install directory, Drupal will refuse to install those two modules. The only exception are install profiles, which are explicitly allowed to override module-shipped configuration, but never the other way around. So in your case you could move the configuration that is now in the profile into a different feature module and then only have either one of them enabled on any given site? If there is some overlap in configuration they could both depend on a "base feature" module to decrease the duplication. That should all work fine with Config Overlay.

Alternatively, you could have modules put their configuration in config/optional but then it really depends on which module gets installed first (and any subsequent modules which provide the same config will be ignored), so for an actual features module this is not ideal either.

I hope this makes sense. I will mark this as "Postponed (maintainer needs more info)" so you can confirm that you are able to resolve the issue and there is in fact no issue to address here. If you do not respond I may just close the issue in the future.

Closing this for now as there is nothing actionable here, as far as I can tell. Feel free to re-open if there is in fact a bug or problem that we can fix.