We upgrade confd from 6.4.3 to 7.2.1. With this change, I am changing corresponding RESTCONF urls. There is no change in yang for this path. I am getting an error in 7.2.1 for this case:
Old Command:
curl -i -H ‘Content-Type: application/vnd.yang.operation+json’ -X POST -d ‘{“input”:{“password”:“abcd”}}’ -u admin:admin http://:/api/config/authentication/edit/local-user-list/local-users/edit/user/user1/_operations/password
New command:
curl -i -H ‘Content-Type: application/yang-data+json’ -X POST -d ‘{“input”:{“password”:“abcd”}}’ -u admin:admin http://:/restconf/data/bluecoat-clp-main:authentication/edit/local-user-list=local-users/edit/user=user1/password
In 7.2.1:
“errors”: {
“error”: [
“error-message”: “Bad format.”,
“error-path”: “/bluecoat-clp-main:authentication/edit/local-user-list=local-users/edit/user=user1/password”,
“error-tag”: “malformed-message”,
“error-type”: “application”

It works fine in 6.4.3. This is the new url. Old equivalent url also works in 6.4.3.

“bluecoat-clp-main:output”: {
“result”: " ok"

Please suggest. Thanks in advance.

If you want to make it easier for people to understand your issue and help, please format your code/json/shell output to make it readable. For example, show some minimum effort by putting three backtick ( ``` ) characters on its own line before and after whatever should be marked as pre-formatted.

my pre-formatted text

Regarding your issue, you seem to want to trigger an action. It would be easier to follow your example if you included the YANG representation the action too.

Search for “action” in the examples.confd/restconf/basic/README for an action example.

RFC 8040 should be your main user- and reference guide for RESTCONF. For example: