Karim Radhouani
Karim Radhouani
That error is coming from the router. Skipping auth works, you just have to omit `--username` and `--password`
Merging YAML files can easily be done with tools like yq: https://mikefarah.gitbook.io/yq/operators/reduce#merge-all-yaml-files-together I think this would be an unnecessary complication for gNMIc.
Something similar was added before see [here](https://github.com/openconfig/gnmic/pull/496) It respawns the whole pod but it will essentially achieve the same result.
Can you share some details on your config, setup and what you are trying to achieve ?
I'm not sure this is a regression, in earlier versions it kept retrying and eventually timed out. With the new version it just fails fast. Running a capabilities request is...
you see it if you add `--debug | -d` to the command: ``` karim@dev1:~$ gnmic version version : 0.38.0 commit : 01ca8fa7 date : 2024-07-11T06:10:14Z gitURL : https://github.com/openconfig/gnmic docs :...
You can set the port together with the address or change the default port using the config file. As far as changing the default port to 9339, I don't see...
I don't see any router using that port as default. I agree with that using defaults simplifies usage, that's if vendors start using it on the server side.
Yes, gNMIc does not look into the error code for Subscribe. That's something that can be enhanced.
Consul discovery does not work that way. The config assigned to a target goes in the config file not in Consul. You register your targets as instances of a Service...