GET RPC call path using the configuration file

[dshah2012]

Hello @karimra ,

I have a question regarding the get and set configuration. Does get and set path is also supported using the file based configuration. If yes, Is there any example configuration file that is present in the repository for the GET RPC call path like we have for the subscription based.

Regards,
Darshan

[karimra]

Hi @dshah2012

Yes both RPCs are supported using file config.

• Get RPC:

get-path: # equivalent to: gnmic get --path
get-type: # equivalent to : gnmic get --type
...

• Set RPC:
  you can follow the same logic as Get RPC ( i.e : $cmd-$flag )
  Or you can use the --request-file format explained here: https://gnmic.kmrd.dev/cmd/set/#template-based-set-request
  the request-file can be static file or a gotemplate rendered against variables supplied using the flag --request-vars

Regards,
Karim

[karimra]

Yes that's fine for testing.
Do you plan to open a PR with this or this is just for you ?

[dshah2012]

Thanks @karimra Yes. I can open a PR once everything is tested .
My CURL looks like this
curl --request POST -H "Content-Type: application/json" -d '{"deviceName":"device_name", "encoding": "json_ietf", "path":"juniper:/configuration/access/address-assignment/"}' http://gnmic_address:port:7890/api/v1/getRPC

[karimra]

ok, I would have a few more requirements in that case :)

• path should be a []string

• DeviceName should be called target

• add a type field, equivalent to the flag --type

• defaults:
  path defaults to []string{"/"}
type defaults to ALL
encoding defaults to JSON

  I think models are not needed for a first draft, and the URI can be changed later on

[karimra]

you curl body json fields need to match the struct tags, or the opposite: change the struct tags to match your curl request body

[dshah2012]

Sure @karimra . Ya now everything works fine.
Just a doubt from different topic The new version is not working when i enter two IP address in the address field in the target section of the target file. If you remember few months back there was a new feature with two IP address so that if one does not work then it tries for the other one.
It works with the old version i was working with. But with this new version that does not work. Not sure if something changed. Could you let me know if it still work?
Because i tried with just one IP it works fine with the new version of the product.