Group Roles Get Deleted

Can you share the result of running drush updb?

After completing a test migration, I've noticed that all Group Roles have been deleted. When the group_content__group_roles table was renamed to group_content__group_roles, it apparently was truncated.

The group_content__group_roles table would be replaced by the group_relationship__group_roles table. But first the "Copy data" step should pass the data from the first table to the second. Once the data has been copied, the "Remove old configurations" step proceeds with deleting the group_content__group_roles table.

Data still exists in my tests after updating. Possibly in your tests something prevented the data from being copied correctly

Sorry. I should have realized this was a false alarm. It does look like something got misconfigured during git operations to bring my test branch up-to-snuff. The output from drush deploy did not report anything unusual in the tests when roles weren't copied. At any rate though, I've been able to rebuild the migration process locally and can try deploying to a shared development environment again.

Apparently I spoke too soon. Something is still not working right as far as roles are concerned. The table isn't truncated, but members' roles aren't showing up on a group's list of members.
I will continue to investigate and report as I find more info.

Could it be related to what was reported in https://www.drupal.org/project/group2to3/issues/3439510 🐛 Members tab doesn't appear on group page and members operation link in group list doesn't work Needs work ?

I have isolated the problem. It is not a defect in this module.

The problem is that I just cannot use this module in the way I would like to, because there is no way to deploy the changes it introduces in a repeatable manner to a higher level environment, at least not with the practices we use.

When the migration takes place, new UUIDs are generated for the replacement/renamed configurations. When I perform the basic procedure on a local environment, everything seems to work just fine, but our workflow has me export the configurations and deploy those to a shared dev environment, then to stage, and finally to prod. That's when things break. I'm guessing here, but I see that the migration generates different UUIDs each time and deploying the configs overwrites them, so there are mismatches that cannot be resolved. Perhaps if the new UUIDs were reproducible/predictable, so that every environment would get the same ones, this wouldn't happen.

At any rate, this module works as described, but just isn't usable by me, and I dare say, by many others, since our workflow is a pretty common one. I'll keep my eyes on this module, in case there's some solution. I do appreciate your work on this, and your prompt attention to the issues I've raised. Thanks.