[CONTROLLER-429] RESTConf API Explorer: Generate URL for augmented nodes Created: 29/Apr/14 Updated: 14/Nov/17 Due: 13/Aug/14 Resolved: 11/Aug/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | restconf |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Abhishek Kumar | Assignee: | Jozef Gloncak |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Mac OS |
||
| Issue Links: |
|
||||||||
| Description |
|
URLs for augmentation are not being generated. |
| Comments |
| Comment by Jozef Gloncak [ 13/Jun/14 ] |
|
I started ODL distribution localy and connected to http://localhost:8080/apidoc/explore. I navigated to section for
Nodes connected, current-capability, initial-capability, pass-through are added to module opendaylight-inventory via augment in module netconf-node-inventory. I can't see problem as was specified by you. Can you be more concrete? |
| Comment by Devin Avery [ 13/Jun/14 ] |
|
If this came from one of my suggestions then I was suggesting that we indicate which attributes / containers etc were provided by a base yang file, and which are those that were provided by an augmentation. That way a user could look at inventory/nodes and see what (and possibly where) all of the extra stuff (metrics, tables, flows etc) come from. |
| Comment by Jozef Gloncak [ 03/Jul/14 ] |
|
Does it mean that the target of this enhancement is only to distinguish generated links for augmentation and for other YANG elements? |
| Comment by Jozef Gloncak [ 15/Jul/14 ] |
|
patch set proposed new behavior: |
| Comment by Jozef Gloncak [ 15/Jul/14 ] |
|
patch set 3 new behavior: |
| Comment by Jozef Gloncak [ 15/Jul/14 ] |
|
it wasn't possible to build patch set. It seems that error is in other project. |
| Comment by Jozef Gloncak [ 31/Jul/14 ] |
|
patch set 5 (rebased) |