Native change data capture (CDC) - CosmosDB change feed is supported in ADF now

Great feature but we run into a strange issue.

Steps to reproduce:

- change a document in cosmosdb

- Run the pipeline that contains de changefeed-enabled dataflow.

- Witness that the monitoring reports that one document is processed.

- change a document in cosmosdb

- Change something in development ADF

- publish towards adf_publish branch which in our case triggers a release towards acceptance

- once deployment is complete to acceptance, run the pipeline again

- The run reports that no changes exist, where one document is expected.

Dataflow source configuration:

After analysis we notice that the arm template creation always changes the pipeline under the hood:

"continuationSettings": {
"customizedCheckpointKey": "9b29c1e3-aaca-4dee-a29f-c464b67b2f34"
}

The customizedCheckpointKey always contains a new/different guid, which is the suspected reason that the changefeed doesn't work any more after release. The documentation suggests that keeping the name of the pipeline and dataflow activity the same is the only requirement to not break the changefeed. But in our case this is not true.