Selective synchronization of users, role mappings, and Zen API keys between existing CPFS/Zen environments

We need a supported mechanism to selectively synchronize specific Foundational Services / Zen configuration and identity data between two already existing and independent environments, primarily Production and Disaster Recovery.

Specifically, we need to synchronize:

Users managed by Foundational Services / Identity Management.

ODM-related user role mappings.

Zen API keys.

The synchronization should be possible from Production to DR and, when required, from DR back to Production, without requiring a full database backup/restore, full environment synchronization, or recreation of the target environment.

Our current CP4BA Production and DR environments use embedded PostgreSQL managed by EDB Postgres for Kubernetes. However, we would like the requested capability to be independent of the underlying PostgreSQL implementation so that it also applies to environments using IBM Cloud Native PostgreSQL (CNPG).

The goal is to provide a documented and supported procedure or product capability to keep these security and identity objects synchronized between existing Production and DR environments, while leaving unrelated Foundational Services / Zen data unchanged.

This capability is particularly important for Disaster Recovery scenarios, where users, role mappings, and API credentials must remain consistent between both environments.

A related CP4BA enhancement request is already open for tracking, and the CP4BA team has identified this requirement as belonging to the Common Foundational Services (CPFS/Zen) component.