Where are the replication domains with base dn set in this setup

[Vibs1956]

https://github.com/ForgeRock/forgeops/blame/c0d8447c051df6d471e143c7e6efc34757213707/docker/ds/ds-setup.sh#L67

Question About Replication Domain Base DN Configuration

While reviewing the replication configuration, I noticed the following section:

set-synchronization-provider-prop --provider-name "Multimaster synchronization"
--set "bootstrap-replication-server:&{ds.bootstrap.replication.servers|localhost:8989}"

Purge delay of 24 hours

set-synchronization-provider-prop --provider-name "Multimaster synchronization"
--set "replication-purge-delay:86400 s"

The create-replication-domain command that specifies the Base DN (cn=admin data) is currently commented out.

I recently created a new backend with its own Base DN, and I want to ensure that it is included in replication.

Questions

Where is the existing logic/configuration that defines the Base DN for replication domains?

Is there another location where replication domains for existing Base DNs are created?

If we introduce a new backend with a new Base DN, do we need to explicitly create a replication domain for it?

I want to understand how the Base DN is currently being passed or configured for replication domains.

[lee-baines]

Apologies for the delayed response. I've asked the questions to our PingDS team and will add the response here.

[lee-baines]

Step 3 in this doc on creating new backends - https://docs.pingidentity.com/pingds/8.1/config-guide/import-export.html#create-database-backend , you would need to manually add a new replication domain for it

The rest of the backends are created via profiles in the upstream image where the replication domains are also created.