<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:53:48 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[YANGTOOLS-618] Deviation statement is not fully available in the YANG parser output</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-618</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;Deviations are currently reported via the Deviation interface and can be retrieved from a Module via getDeviations().&lt;/p&gt;

&lt;p&gt;However, not all information of the deviation can be retrieved.&lt;/p&gt;

&lt;p&gt;For example, for the following deviation example from the RFC:&lt;/p&gt;

&lt;p&gt;     deviation /base:system/base:user/base:type {&lt;br/&gt;
         deviate add &lt;/p&gt;
{
             default &quot;admin&quot;; // new users are &apos;admin&apos; by default
         }
&lt;p&gt;     }&lt;/p&gt;

&lt;p&gt;the YANG parser returns a Deviation object, in which the getDeviate() method only returns an enum &lt;br/&gt;
NOT_SUPPORTED(&quot;not-supported&quot;), ADD(&quot;add&quot;), REPLACE(&quot;replace&quot;), DELETE(&quot;delete&quot;)&lt;/p&gt;

&lt;p&gt;The details for the deviation (in this example, that a default is added) are not available, so systems using the YANG parser cannot use this information.&lt;/p&gt;

&lt;p&gt;So at the very minimum all the information from the deviation statement should be made available in the parser.&lt;/p&gt;

&lt;p&gt;Would it however also be possible to transparently update the target nodes with the deviations?   i.e. in the above example, the default value of the &quot;type&quot; DataSchemaNode could be transparently updated, so that applications don&apos;t have to process the deviations separately.   &lt;/p&gt;

&lt;p&gt;If I understand the YANG RFC correctly, a deviation is not automatically active: you have to announce via the hello capabilities that you are using certain deviations.   So probably this should be done in the same way as in the if-feature case (&lt;a href=&quot;https://bugs.opendaylight.org/show_bug.cgi?id=4506&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://bugs.opendaylight.org/show_bug.cgi?id=4506&lt;/a&gt;).&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="23038">YANGTOOLS-618</key>
            <summary>Deviation statement is not fully available in the YANG parser output</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="ifoltin">Igor Foltin</assignee>
                                    <reporter username="verthezpw">Peter Verthez</reporter>
                        <labels>
                    </labels>
                <created>Tue, 7 Jun 2016 10:34:36 +0000</created>
                <updated>Sun, 10 Apr 2022 18:35:47 +0000</updated>
                            <resolved>Mon, 25 Jul 2016 08:06:55 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="43911" author="ifoltin" created="Thu, 23 Jun 2016 11:35:44 +0000"  >&lt;p&gt;fix pushed:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/40752/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/40752/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="43912" author="verthezpw" created="Mon, 25 Jul 2016 06:23:10 +0000"  >&lt;p&gt;So are the target nodes now transparently updated?  I didn&apos;t see any discussion on that, and I would like to know what has been implemented.&lt;/p&gt;</comment>
                            <comment id="43913" author="ifoltin" created="Mon, 25 Jul 2016 08:03:49 +0000"  >&lt;p&gt;The patch above changed the deviation statement API so that it now provides more info about the deviation (for example, that a default is added, replaced etc). Moreover, the deviation statement now contains a list of deviate substatements instead of just one deviate. &lt;/p&gt;

&lt;p&gt;Please, see this: &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://wiki.opendaylight.org/view/Weather#Change_of_deviation_statement_API_in_yangtools&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://wiki.opendaylight.org/view/Weather#Change_of_deviation_statement_API_in_yangtools&lt;/a&gt; &lt;/p&gt;


&lt;p&gt;The next step, i.e. updating deviation target node according to deviate(s)) will be addressed separately - &lt;a href=&quot;https://bugs.opendaylight.org/show_bug.cgi?id=6261&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://bugs.opendaylight.org/show_bug.cgi?id=6261&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="43914" author="verthezpw" created="Mon, 25 Jul 2016 08:06:55 +0000"  >&lt;p&gt;OK, thanks.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>6022</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=6022]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10308"><![CDATA[New Feature]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10310"><![CDATA[Boron-M5]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i028c7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>