Default value for config=false leafs about sysrepo HOT 5 OPEN

This is very implementation-dependent, works as intended, and is the result of different handling of configuration and state data. Default configuration data are populated "automatically" while any state data need to be provided by one of the methods.

from sysrepo.

Do you want to say that it is always works this way or we can just change method pull to push?

from sysrepo.

I only said that if you want to get default state nodes in the operational datastore, you can use pull or push method of populating the operational datastore.

from sysrepo.

If any state data need to be provided by one of the methods, why in example below sysrepo works like this?
There are no providers of data, so i didn't get why can I see default value of test1 leaf this way?

root@cb1:~# cat r.yang
module examples {
  yang-version 1.1;
  namespace "urn:examples";
  prefix e;

  container test {
    leaf test1 {
      type string;
      config false;
      default "test";
    }
  }
}
# sysrepoctl -i r.yang
# sysrepocfg -X -d operational -m examples
<test xmlns="urn:examples">
  <test1>test</test1>
</test>

Seems like it is a bug and leaf shouldn't exist in operational data until someone subscribes to it

from sysrepo.

You are right about that, not sure how the code got wrong, should be fixed, though.

from sysrepo.