use of existing database along with custom ldif files at startup - behaviour

[gilmojoa]

if the container is run with existing database mounted as volume, and seed data (ldif files within ../bootstrap/custom/..) are also mounted on startup, it seems the custom ldif seed data are ignored? unless the mounted database is non existent and created as new volume, in which case the ldif seed data will be added to the new database. is this expected behaviour? Trying to understand, in order to determine best approach for adding/removing users to existing ldap server instance.