get ignores not-yet-committed data

[jktjkt]

By default, the CLI operates on a "virtual datastore" which redirects writes to a "datastore that accepts writing" and reads to a "datastore that returns operational data". In the NETCONF implementation, this means that writes go to either startup or candidate, while reads are from either operational or running or startup. The intention is to make sure that get can print live non-config data, but the implementation is super confusing. For example, I can set something, but a get would not return that data by default.

One possible fix would be to implement separate "edit mode" vs. "read mode", and access the datastores without any fancy mapping. Another option would be some local caching of the data. The ergonomics have to be well thought-out.