Prevent CDK from creating a new OpenSearch domain

I modified some parameters of our OpenSearch domain and did a new CDK deploy. Turns out that CDK decided to create a new cluster and redirect both the lambda that performs search and Fargate task that indexes to this new cluster. So now I have a cluster with 100k documents that is not connected to anything and a search cluster that doesn't have any index or documents.

I assume I should be able to do a back up of the old cluster and apply that backup to the new cluster. This will fix my current situation since this is our development cluster. However, if this was our production cluster, we would have downtime. Ideally, there should be a way of rolling back the Cloud Formation stack or importing the old domain into the stack, but none of those options seem to be available.

I don't know why CKD decided to create a new domain. It could be because the existing domain was updated and CDK specified an earlier version or it could be related to the security policy changes I added. I assume it's the latter since reverting them resulted in the creation of a third cluster.

Is there a way to prevent CDK from creating new search domains like this?