[OVSDB-265] ovsdb.yang uses "mandatory" statement inappropriately Created: 20/Jan/16 Updated: 10/Mar/16 Resolved: 10/Mar/16 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | Southbound.Open_vSwitch |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Ryan Goulding | Assignee: | Ryan Goulding |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
Since the parent container is non-presence, adding mandatory has unintended behavior. |
| Comments |
| Comment by Vratko Polak [ 29/Jan/16 ] |
|
Which container? Every mandatory leaf I see in ovsdb.yang has "list" (as opposed to "container") as its closest ancestor. |
| Comment by Ryan Goulding [ 10/Mar/16 ] |
|
Talked with some more YANG experts on my side. What we concluded is that "not a non-presence container" means skip containers until you find a presence container or any other structured type. Since a list is a structured type, mandatory should be fine in this case. |