Overridden config right after site install

1. But a config import would delete any new Roles, not present in the export.
2. Agree needs to be addressed.

But a config import would delete any new Roles, not present in the export.

Thanks for continuing the discussion. I still have some questions:

1) How can we be sure that this is true? ConfigInstallerInterface::setSyncing() can be called by any code. It is set when installing a module in ModuleInstaller::install(), which would presumably not delete any roles.

2) If the config import does delete roles no present in the export, how come config is overridden? It seems to me like this:

• If a role is missing from administerusersbyrole.settings, this module will cause a config override, and this is correct.
• If no role is missing, this module will not cause a config override.

So I don't understand when there is a problem.

Hm - i just came to evaluate this module and left a comment.
So next step is to reproduce the Issue on my side.

I just had an idee to avoid administerusersbyrole.settings at all. Attach the configuration to each role config via third_party_settings.

Patch changed according to the changes introduced in version 3.4.

Patch changed according to the changes introduced in version 3.4.

Hiding outdated patch.

Same issue runing v3.4 on Drupal 10.1.2. Patch in #9 fixes the issue. Thanks!