This page documents a legacy topology. Do not use it as a deployment guide for Midaz v4.
/v2/organizations/{organization_id}/.... The Ledger is the current deployment unit. CRM is not a plugin, standalone service, or separate v4 release.
Helm compatibility versus v4
The Helm repository still contains a crm.enabled compatibility workload (midaz-crm, port 4003) for older application images. It is legacy compatibility, not the v4 model. The repository does not contain a current plugin-crm chart. Do not introduce plugin-crm, crm.enabled, port 4003, X-Organization-Id, or legacy CRM v1 alias endpoints into a v4 installation.
The plugin-fees chart also remains for legacy deployments. Fees in Midaz v4 runs in the Ledger and is available only on /v2.
If you retire an older standalone CRM deployment, retain its MongoDB backup and release values. Then reconcile Holder and Instrument records through the Ledger /v2 API before you decommission the old workload. Preserve that release record. Do not apply its values to a new v4 Ledger release.
See CRM getting started and Midaz Helm installation.
