`sr_module_change_subscribe` appears to provide config data in the operational datastore about sysrepo HOT 3 CLOSED

This is as per the docs. The reasoning matches how the NMDA is designed: the operational DS should reflect config which "is in effect". If there's an active subscription, chances are that it's doing something in response to any changes, so they are "in effect", and therefore it makes sense to auto-propagate the running DS to operational.

from sysrepo.

Thank you, I can see the reasoning. I was just surprised because I have a plugin that subscribes to some sub-tree of my module and the rest of the module was not showing up in the operational datastore output. Just because I didn't subscribe to a particular part of my datastore doesn't mean I'm not using it. To achieve what I want, I do need to add this "no-op subscription" that's just an empty function just to get sysrepo to output the data.

from sysrepo.

Just because I didn't subscribe to a particular part of my datastore doesn't mean I'm not using it.

This is not normally the case and the expectation is that you will to adjust the behavior somehow if you are using a configuration subtree, which means you will have a subscription for it. But I suppose there may be some special use-cases when this is not the case.

from sysrepo.