Operating System: All
Platform: All

1 & 2 : If you are configuring through mdsal(topology model) you won't find the configuration in config subsystem. If you want to see how the current configuration that's in netconf topology just switch operational to config in the restconf url you used to configure the connector in the first place.

/controller-config/yang-ext:mount/config:modules/ is a separate entity and you won't find connectors that are configured in topology here. Same applies to the opposite - you won't find configuration that's in cfg subsystem in netconf-topology.

3. you were probably looking at controller-config connector configuration since connectors configured through topology are not present here.

All in all seems like user error to me.

Closing as resolved invalid, since as Tomas pointed out config from topology is not moved to sal-netconf-connector-cfg, since this is separate way to configure NETCONF devices and was never intended to be synchronized.

Given that the old mechanism is present and not deprecated in Beryllium, is is really fair to make this invalid? I'd think not?

Configuration through topology is meant to bypass cfg subsystem entirely. I'll try to summarize the steps quickly and go over whats wrong.

1. post configuration to mdsal
2. look into cfg subsystem for the configuration which was just posted
3. the newly posted config is not present since it's in mdsal

mdsal and cfg subsystem are 2 separate entities and are not meant to be mirrored/synchronized. When you post configuration to the topology datastore it's going to be present in the topology datastore. You don't want to tangle these 2 systems together.

(In reply to Colin Dixon from comment #3)
> is really fair to make this invalid? I'd think not?

Colin I'm not sure what you mean by this, but the bug report here has an incorrect assumption of mdsal/cfg subsystem and hence is user error.