Hi,

I'm running into a problem where my YANG is being rejected by a NETCONF client 
that claims it can't find the node being augmented.  The YANG snippet below 
shows the problem which relates specifically to augmenting a node that is 
'config false'.  AFAICT from reading RFC 6020, this is valid YANG, but I would 
appreciate confirmation from the experts!

Pyang is quite happy with this.

Thanks,

William

--- sample yang to show problem ---

                grouping state-grouping {
                                container state {
                                                config false;
                                                leaf state-grp-state-leaf {
                                                                type string;
                                                }
                                }
                }

                container test {
                                container state-cont {
                                                config false;
                                                leaf state-leaf {
                                                                type string;
                                                }
                                }
                }

                augment /test/state-cont {
                                // Augment 'config false' container directly 
works.
                                leaf augmented-state-leaf {
                                                type string;
                                }
                }

                augment /test {
                                uses state-grouping {
                                                // Augment here fails - 'state' 
not found.
                                                augment state {
                                                                leaf 
aug-state-grp-leaf {
                                                                                
type string;
                                                                }
                                                }
                                }
                }


_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to