There is a module which has very deep uses grouping stack. In a certain level, there defines an augment which augmented a container which defined in an grouping.
module ik {
grouping ct_akpwcg {
container pkt {
leaf lf_hpri_key {
type empty;
}
}
}
grouping ks_akpwcg {
uses ct_akpwcg {
augment pkt {
container c_en_pri_key {
uses evg;
}
}
}
}
grouping evg {
leaf value {
type binary;
}
}
uses ks_akpwcg;
// Deviation Target: ug is short for uses-grouping
// /pkt (container-in-ug<ct_akpwcg>-in-ug<ks_akpwcg>)
// /lf_hpri_key (leaf)
//
deviation /pkt/lf_hpri_key {
deviate not-supported;
}
// Deviation Target: ug is short for uses-grouping
// /pkt (container-in-ug<ct_akpwcg>-in-ug<ks_akpwcg>)
// /c_en_pri_key (container-in-augmented-container-of-pkt-in-ug<ct_akpwcg>-under<ks_akpwcg>)
//
deviation /pkt/c_en_pri_key {
deviate not-supported;
}
}
There are two deviation's
/pkt/lf_hpri_key should point to the leaf defined in the original container pkt of grouping ct_akpwcg
/pkt/c_en_pri_key should point to the leaf augmented from the augement pkt in uses ct_akpwcg.
Actually, the leaf c_en_pri_key in second path couldn't be linked correctly.
Here is the test case.
AugmentInDeepUsesGroupingTest.txt
According to debug, I think this is a tricky issue.
There missing some logic in ScopeContextProvider.
There is a module which has very deep uses grouping stack. In a certain level, there defines an augment which augmented a container which defined in an grouping.
There are two deviation's
Actually, the leaf c_en_pri_key in second path couldn't be linked correctly. Here is the test case. AugmentInDeepUsesGroupingTest.txt
According to debug, I think this is a tricky issue. There missing some logic in ScopeContextProvider.