[CONTROLLER-1560] Can't GET default module configuration by RESTCONF Created: 24/Oct/16 Updated: 25/Jul/23 |
|
| Status: | Confirmed |
| Project: | controller |
| Component/s: | blueprint |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | ||
| Reporter: | Tomas Janciga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| Description |
|
GET requests for the current configuration of blueprint modules don't work with default configuration. Example of the GET reqest URL and response body: GET: localhost:8181/restconf/config/onem2m-plugin-loader-config:onem2m-plugin-loader-config { ] |
| Comments |
| Comment by Tomas Janciga [ 24/Oct/16 ] |
|
Attachment file_7012.txt has been added with description: Yang model and Blueprint XML |
| Comment by Tom Pantelis [ 04/Jul/17 ] |
|
Default configuration is just that - it is only provided to the app if there is no data in the datastore and thus, if not present in the datastore, it won't be reported via restconf. |
| Comment by Robert Varga [ 14/Nov/18 ] |
|
tjanciga is this still present in Neon? If so, can you provide steps to reproduce? |
| Comment by Tom Pantelis [ 14/Nov/18 ] |
|
This is referring to the clustered-app-config BP extension - when provided with a default config, it is not returned from RESTCONF b/c it is not actually written to the DS. For RESTCONF to report it would require some hook somewhere in the DS. |
| Comment by Robert Varga [ 14/Nov/18 ] |
|
... or an automagically-populated DS shard (assuming DOMDataTreeService). |
| Comment by Tom Pantelis [ 14/Nov/18 ] |
|
yes - that would be the hook... |