Hi, the helm chart uses the OSS PeerDB images.
The sh files were created to bootstrap the values files for easier (and faster) POCs.
You can append a `template` argument when running the script files which will lead to a set of values file being generated, which you can then modify accordingly.
There is a production guide for the same as we have customers in production using GitOps (ArgoCD) with the provided charts (https://github.com/PeerDB-io/peerdb-enterprise/blob/main/PRO...)
Additionally, it can help with systems where 2-phase commits can lead to weird and complex situations. This is where applying SAGA and using Transactional Outbox can help: it should allow for abstracting away the event stream away from the main application logic, the CDC mirror can then handle generating the stream.
This can also allow for plug-and-play of other downstream services/sinks from the CDC stream.
You can append a `template` argument when running the script files which will lead to a set of values file being generated, which you can then modify accordingly. There is a production guide for the same as we have customers in production using GitOps (ArgoCD) with the provided charts (https://github.com/PeerDB-io/peerdb-enterprise/blob/main/PRO...)