Seed is ignored on an existing instance and behaves inconsistently on "seeded" objects

[xeals]

I have a small system that I'm playing around with having a combination of seeded and non-seeded users and groups. I started initially with the default NixOS seed (admin and Dex search user) and have added to it over time.

I have so far noticed the following:

• Users and groups present in the seed are not added to the database.json or slapd (confirmed both in logs and by attempting to authenticate against them, as well as obviously not appearing in the UI)
• Users and groups are not updated based on changes made in the seed
• Users can be created through the UI with an ID matching a seed with no issue
  • Attempting to modifying such users with seed-defined attributes fails
  • Attempting to delete such users displays a success message but the user remains present (this is consistent for users that are actually seeded)
• Groups cannot be created through the UI with an ID matching a seed; attempting to do so displays a success message but nothing happens
• Seeded groups can have users added to them through the UI, but not removed; no changes to memberships are made when "re-seeding"

Using v1.1.0.
Current seed.json for reference.

[majewsky]

I merged a near-complete rewrite of the core logic today. Most or all of the issues you describe should be addressed by this change, since behaviors related to seeding are now validated through automated tests. There are still cleanups that I still want to do; once the next release drops, I'd be interested in hearing from you regarding your observations with the new release.