When tab completing list keys, the entries that I've created previously, but not yet committed, are not offered:
line-M0N ~ # netconf-cli-local
Connected via NETCONF [datastore target: operational]
/> set czechlight-roadm-device:channel-plan/channel[name='X']/upper-frequency 194000000
/> set czechlight-roadm-device:channel-plan/channel[name='X']/lower-frequency 193000000
/> set czechlight-roadm-device:channel-plan/channel[name='
Display all 144 possibilities? (y or n)
'13.5' '21.5' '29.5' '37.5' '45.5' '53.5'
'14 (100GHz)' '22 (100GHz)' '30 (100GHz)' '38 (100GHz)' '46 (100GHz)' '54 (100GHz)'
'14.0' '22.0' '30.0' '38.0' '46.0' '54.0'
'14.5' '22.5' '30.5' '38.5' '46.5' '54.5'
'15 (100GHz)' '23 (100GHz)' '31 (100GHz)' '39 (100GHz)' '47 (100GHz)' '55 (100GHz)'
'15.0' '23.0' '31.0' '39.0' '47.0' '55.0'
'15.5' '23.5' '31.5' '39.5' '47.5' '55.5'
'16 (100GHz)' '24 (100GHz)' '32 (100GHz)' '40 (100GHz)' '48 (100GHz)' '56 (100GHz)'
'16.0' '24.0' '32.0' '40.0' '48.0' '56.0'
'16.5' '24.5' '32.5' '40.5' '48.5' '56.5'
'17 (100GHz)' '25 (100GHz)' '33 (100GHz)' '41 (100GHz)' '49 (100GHz)' '57 (100GHz)'
'17.0' '25.0' '33.0' '41.0' '49.0' '57.0'
'17.5' '25.5' '33.5' '41.5' '49.5' '57.5'
'18 (100GHz)' '26 (100GHz)' '34 (100GHz)' '42 (100GHz)' '50 (100GHz)' '58 (100GHz)'
'18.0' '26.0' '34.0' '42.0' '50.0' '58.0'
'18.5' '26.5' '34.5' '42.5' '50.5' '58.5'
'19 (100GHz)' '27 (100GHz)' '35 (100GHz)' '43 (100GHz)' '51 (100GHz)' '59 (100GHz)'
'19.0' '27.0' '35.0' '43.0' '51.0' '59.0'
'19.5' '27.5' '35.5' '43.5' '51.5' '59.5'
'20 (100GHz)' '28 (100GHz)' '36 (100GHz)' '44 (100GHz)' '52 (100GHz)' '60 (100GHz)'
'20.0' '28.0' '36.0' '44.0' '52.0' '60.0'
'20.5' '28.5' '36.5' '44.5' '52.5' '60.5'
'21 (100GHz)' '29 (100GHz)' '37 (100GHz)' '45 (100GHz)' '53 (100GHz)' '61.0'
'21.0' '29.0' '37.0' '45.0' '53.0' 'C-band'
/> set czechlight-roadm-device:channel-plan/channel[name='
This is different form #8; that bug deals with the existing data vs. possible data, while this one is about uncommitted vs. committed data.
When tab completing list keys, the entries that I've created previously, but not yet committed, are not offered:
This is different form #8; that bug deals with the existing data vs. possible data, while this one is about uncommitted vs. committed data.