https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/YANGTOOLS-1526 yangtools <p>According to <a href="https://datatracker.ietf.org/doc/html/rfc7950#section-7.8.2" class="external-link" target="_blank" rel="nofollow noopener">https://datatracker.ietf.org/doc/html/rfc7950#section-7.8.2</a> a configuration list must have a key:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>The "key" statement, which MUST be present if the list represents configuration and MAY be present otherwise, takes as an argument a string that specifies a space-separated list of one or more leaf identifiers of this list.</pre> </div></div> <p>But we can create model which contains unkeyed config list as shown in <a href="https://jira.opendaylight.org/browse/NETCONF-1082" title="Unable to write unkeyed list with RESTCONF PUT request" class="issue-link" data-issue-key="NETCONF-1082"><del>NETCONF-1082</del></a>. </p> <p> </p> YANGTOOLS-1526

Unkeyed config list is not rejected

Bug Medium Resolved Won't Do Robert Varga Ivan Hrasko Fri, 21 Jul 2023 11:49:26 +0000 Fri, 21 Jul 2023 14:04:57 +0000 Fri, 21 Jul 2023 13:08:25 +0000 0 1 <p>This absolutely intentional. The quoted restriction is a leak from NETCONF protocol (i.e. addressability). See <a href="https://jira.opendaylight.org/browse/YANGTOOLS-1423" title="Do not warn about unkeyed config=true lists by default" class="issue-link" data-issue-key="YANGTOOLS-1423"><del>YANGTOOLS-1423</del></a> et al.</p> <p>If you need the ability to optionally reject such models, this needs to change YangParserConfiguration.warnForUnkeyedLists() to allow specifying policy. Also the implementation of that flag needs to be reworked to address <a href="https://jira.opendaylight.org/browse/YANGTOOLS-1186" title="Remove EffectiveStmtCtx.cearbannog()" class="issue-link" data-issue-key="YANGTOOLS-1186">YANGTOOLS-1186</a> and work during inference rather than during buildEffective().</p> Development Rank 0|i045vr: