Currently the consumer group name in change-prop is hardcoded into the sources. In order to run k8s deployment of change-prop and scb deployment in parallel and test things, we need to make the consumer group prefix configurable. I propose to use service name instead of the hardcoded 'change-prop' string. See for example how the retry stream name is constructed - we need to do the same.
Code-wise this is easy, but changing the consumer group names in production will be messy. When deployed with new consumer groups names, change-prop will not find any committed offsets for it's new group, so it will start from the latest offset, effectively skipping the backlog. So, when deploying the change we need to roll it out on half of the nodes first and wait for at least the highest backlog. This will cause duplicate message processing, but we can rely on deduplicator-by-id to get rid of duplicates. Also, updates are idempotent, so some duplication is not a huge problem.
Ping me on IRC if you have questions. Please do the coding part, we can do the deployment together.