Fix identityref namespace binding in config-path-info XML#649
Fix identityref namespace binding in config-path-info XML#649olofhagsand merged 1 commit intoclicon:masterfrom
Conversation
|
I am unsure, did you do this patch after the new series of commits that move yang-dependent functionality from the cli client to the backend I did friday, see eg 046886a ? With these commits, the YANG is not present in the client and the identityref adds should be done by the backend. However, I see the patch in If I am right then with my new commits on friday, it should be enough with the identityref_add_ns patch and not the cli_dbxml patch to run your openconfig testcase. Does that make sense? |
|
I just retested on the latest master my test case fails without my changes |
|
The patch you referenced doesn’t touch the edit‑config payload, so the prefix is still missing when validation runs. That’s why the CLI‑side bind+apply is effective (and also why a backend‑side fix must be placed in the edit‑config processing path, not in config‑path‑info). Do you strongly prefer backend-only fix? |
0fb4f7a to
287be96
Compare
|
Binding YANG on CLI indeed is not needed. |
|
Can you please make the test executable? |
Ensure identityref values with prefixed QNames get the correct xmlns binding
287be96 to
335a18f
Compare
|
Sorry, my bad again with +x. Added validate and RESTCONF tests |
Bind YANG on CLI edit-config XML before sending RPC and add missing xmlns for identityref values. Extend identityref namespace helper to cover leaf-lists and allow yspec fallback.