Mongock migration for MongoDB on CosmosDB fails about mongock

[osantana85]

Hello @hans009 , thanks for raising the issue and for your workaround. We'll take it into account to update Mongock's documentation.

[hans009]

Hello again, I found out that it's related to MongoDB on CosmosDB (non-vCore) inability to span transactions accross multiple collections.
The issue is that after executing a change unit (e.g. adding something to collection_one) the mongockChangeLog collection should get updated within the same transaction and thus fails due to that limitation.
So maybe you can add to your CosmosDB documentation that in the non-vCore mode you cannot use native transactions in that scenario but instead have to implement the rollback logic in @RollbackExecution method yourself