Event Stream Disabled In Main Branch But Enabled In Sub-Branch Using Git Integration Draining CUs

[scca]

I'm trying out Git Integration here to implement better version control but just now I realised that event streams that I have disabled in the workspace that's tied to my "main" branch is enabled in the other workspace that's connected to my "working branch". Best part? I didn't even know this until someone on my team caught that CU consumption shot up out of the blue. This caught me by surprise as I'd have expected the git sync process to cover even the if something was "on or off". Does anyone know if this is expected behaviour of git integration? It makes no sense to me. Imagine if I have a feature to work on and I branched out to a new workspace, work on it for days without knowing this and it just ate my CUs dry. It's even worse if you consider multiple developers working off the same workspace (i.e. each branching out to their own). 

[v-ssriganesh]

Hi @scca,
Thank you for posting your query in the Microsoft Fabric Community Forum.

Git integration only versions the metadata/definition of items (such as the Eventstream object and its configuration). It does not synchronize the runtime state, including whether an Eventstream is started or stopped.

As a result, after syncing to a dev or feature-branch workspace, it’s important to explicitly verify and stop Eventstreams (and other runtime artifacts) to avoid unintended CU consumption. Using separate low-capacity dev workspaces and maintaining a post-sync checklist can also help prevent this.

Best regards,
Ganesh Singamshetty.